From: "hugh.dickins@tiscali.co.uk" <hugh.dickins@tiscali.co.uk>
To: Bo Liu <bo-liu@hotmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [RFC]get_swap_page():delay update swap_list.next
Date: Mon, 19 Oct 2009 17:16:33 +0100 (GMT+01:00) [thread overview]
Message-ID: <29949019.1255968993574.JavaMail.root@ps29> (raw)
On Mon, 19 Oct 2009 you wrote:
> If scan_swap_map() successed in current si, there is no
> need to update swap_list.next.So get_swap_page next time
> called can start search from the last swap_info(which still
> have free slots).
No, I think you'll find that's mistaken. It is intended behaviour that
allocating from two swap areas of the same priority will alternate
between them page by page (or cycle around three or more of
the same priority) - a kind of poor man's striping.
You may think that's silly, and not want that behaviour: in which
case assign different priorities to those swap areas, and it will
then behave like you were changing the same priority case to
behave. So there is no reason to make your change.
Hugh
[I apologize for breaking the threading on your mail: I've been
caught by surprise to find myself unable to reply in the usual way.]
Get 50% off Norton Security- http://www.tiscali.co.uk/securepc
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2009-10-19 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 16:16 hugh.dickins [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-19 6:38 [RFC]get_swap_page():delay update swap_list.next Bo Liu
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=29949019.1255968993574.JavaMail.root@ps29 \
--to=hugh.dickins@tiscali.co.uk \
--cc=akpm@linux-foundation.org \
--cc=bo-liu@hotmail.com \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).