linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: linux-mm@kvack.org, mgorman@suse.de
Subject: Re: [PATCH] mm: swap: Use swapfiles in priority order
Date: Thu, 13 Feb 2014 17:27:08 +0100	[thread overview]
Message-ID: <52FCF25C.9010802@linux.vnet.ibm.com> (raw)

Hi,
first of all I hope this patching in of the Mesage-ID works for threaded 
views :-)

On 13/02/14 10:42:31, Mel Gorman wrote:
 >
 >
 > [prev in list] [next in list] [prev in thread] [next in thread]
 >
 > List:       linux-mm
 > Subject:    [PATCH] mm: swap: Use swapfiles in priority order
 > From:       Mel Gorman <mgorman () suse ! de>
 > Date:       2014-02-13 10:42:31
 > Message-ID: 20140213104231.GX6732 () suse ! de
 > [Download message RAW]
 >
 > According to the swapon documentation
 >
 > 	Swap  pages  are  allocated  from  areas  in priority order,
 > 	highest priority first.  For areas with different priorities, a
 > 	higher-priority area is exhausted before using a lower-priority area.
 >
 > A user reported

That was me and I can confirm that for all my setup were we encountered 
the issue is fixed with the new patch.

On top of that it also fixed a long running issue that swap gets slower 
the more swap targets you have - which was formerly discussed in detail 
here http://www.spinics.net/lists/linux-mm/msg68624.html

 > that the reality is different. When multiple swap files
 > are enabled and a memory consumer started, the swap files are consumed in
 > pairs after the highest priority file is exhausted. Early in the lifetime
 > of the test, swapfile consumptions looks like
 >
[...]
 >
 > Signed-off-by: Mel Gorman <mgorman@suse.de>
 > ---
 >  mm/swapfile.c | 2 +-
 >  1 file changed, 1 insertion(+), 1 deletion(-)
 >
 > diff --git a/mm/swapfile.c b/mm/swapfile.c
 > index 4a7f7e6..6d0ac2b 100644
 > --- a/mm/swapfile.c
 > +++ b/mm/swapfile.c
 > @@ -651,7 +651,7 @@ swp_entry_t get_swap_page(void)
 >  		goto noswap;
 >  	atomic_long_dec(&nr_swap_pages);
 >
 > -	for (type = swap_list.next; type >= 0 && wrapped < 2; type = next) {
 > +	for (type = swap_list.head; type >= 0 && wrapped < 2; type = next) {
 >  		hp_index = atomic_xchg(&highest_priority_index, -1);
 >  		/*
 >  		 * highest_priority_index records current highest priority swap


--
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>

             reply	other threads:[~2014-02-13 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 16:27 Christian Ehrhardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-13 10:42 [PATCH] mm: swap: Use swapfiles in priority order Mel Gorman
2014-02-13 15:58 ` Weijie Yang
2014-02-14 10:17   ` Mel Gorman
2014-02-14 13:33     ` Weijie Yang
2014-02-14 13:10   ` Christian Ehrhardt
2014-02-16  2:59     ` Weijie Yang
2014-02-24  8:28       ` Hugh Dickins

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=52FCF25C.9010802@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=20140213104231.GX6732@suse.de \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    /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).