From: hugang@soulinfo.com
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@suse.cz>, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] swsusp: speed up image restoring on x86-64
Date: Fri, 21 Jan 2005 22:31:37 +0800 [thread overview]
Message-ID: <20050121143136.GA19036@hugang.soulinfo.com> (raw)
In-Reply-To: <200501211442.55274.rjw@sisk.pl>
On Fri, Jan 21, 2005 at 02:42:54PM +0100, Rafael J. Wysocki wrote:
> Hi,
>
>
> No, it's "repeat until %ecx is zero or ZF is cleared", but the latter never happens
> with movsl. It's intended for cmpsl, scasl and friends (the assembler should
> complain about using it here).
>
> > I think this should be "rep movsl".
>
> Yes, it should.
>
I'll change my code.
>
> I have a suggestion.
>
> hugang, you are currently replacing an array of pbes with a list of arrays
> of pbes contained within individual pages.
>
> I would go further and replace it with a single one-directional list
> of pbes. Namely, I would modify "struct pbe" in the following way:
>
> struct pbe {
> unsigned long address;
> unsigned long orig_address;
> swp_entry_t swap_address;
> struct pbe *next;
> };
>
> (AFAICT, the "dummy" field is only used by hugang - as a pointer)
> and I would define "for_each_pbe()" as:
>
> #define for_each_pbe(pbe, pblist) \
> for (pbe = pblist; pbe; pbe = pbe->next)
>
> Then, the only non-trivial changes would be in alloc_pagedir() and
> in swsusp_pagedir_relocate(), where I would need to link pbes to
> each other.
>
> This also would make the assembly parts independent of the
> sizeof(struct pbe), which is currently hardcoded there.
>
> What do you think?
Thanks for point that, That's better solution than current, I'll change
current code to this.
I'm think about, how can I make chang smaller.
--
Hu Gang .-.
/v\
// \\
Linux User /( )\ [204016]
GPG Key ID ^^-^^ http://soulinfo.com/~hugang/hugang.asc
next prev parent reply other threads:[~2005-01-21 14:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 19:32 Rafael J. Wysocki
2005-01-20 20:59 ` Pavel Machek
2005-01-20 21:46 ` Rafael J. Wysocki
2005-01-20 22:06 ` Pavel Machek
2005-01-20 22:58 ` Rafael J. Wysocki
2005-01-20 23:06 ` Pavel Machek
2005-01-21 0:14 ` Rafael J. Wysocki
2005-01-21 10:06 ` Pavel Machek
2005-01-21 12:43 ` Rafael J. Wysocki
2005-01-21 2:23 ` hugang
2005-01-21 10:04 ` Pavel Machek
2005-01-21 10:19 ` Andi Kleen
2005-01-21 10:30 ` Pavel Machek
2005-01-21 13:42 ` Rafael J. Wysocki
2005-01-21 14:31 ` hugang [this message]
2005-01-21 17:48 ` Pavel Machek
2005-01-21 12:32 ` Rafael J. Wysocki
2005-01-21 19:09 ` Rafael J. Wysocki
2005-01-22 2:03 ` Andi Kleen
2005-01-20 21:04 ` Rafael J. Wysocki
2005-01-22 2:50 ` Andi Kleen
2005-01-22 9:54 ` Pavel Machek
2005-01-22 11:26 ` Andi Kleen
2005-01-22 11:30 ` Pavel Machek
2005-01-22 11:44 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050121143136.GA19036@hugang.soulinfo.com \
--to=hugang@soulinfo.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome