From: "Pádraig Brady" <P@draigBrady.com>
To: Alex Shi <alex.shi@intel.com>
Cc: linux-mm@kvack.org, mgorman@suse.de,
linux-kernel@vger.kernel.org, andrea@cpushare.com,
tim.c.chen@intel.com, shaohua.li@intel.com,
akpm@linux-foundation.org, riel@redhat.com, luto@mit.edu
Subject: Re: [PATCH] kswapd: avoid unnecessary rebalance after an unsuccessful balancing
Date: Fri, 29 Jul 2011 19:21:49 +0100 [thread overview]
Message-ID: <4E32FA3D.5060100@draigBrady.com> (raw)
In-Reply-To: <1311952990-3844-1-git-send-email-alex.shi@intel.com>
On 07/29/2011 04:23 PM, Alex Shi wrote:
> In commit 215ddd66, Mel Gorman said kswapd is better to sleep after a
> unsuccessful balancing if there is tighter reclaim request pending in
> the balancing. In this scenario, the 'order' and 'classzone_idx'
> that are checked for tighter request judgment is incorrect, since they
> aren't the one kswapd should read from new pgdat, but the last time pgdat
> value for just now balancing. Then kswapd will skip try_to_sleep func
> and rebalance the last pgdat request. It's not our expected behavior.
>
> So, I added new variables to distinguish the returned order/classzone_idx
> from last balancing, that can resolved above issue in that scenario.
>
> I tested the patch on our LKP system with swap-cp/fio mmap randrw
> benchmarks. The performance has no change.
>
> Padraig Brady, would you like to test this patch for your scenario.
This
+ your previous 2 line patch
+ Mel's 3 patches
+ 2.6.38.4
still works fine for me.
cheers,
Padraig.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-07-29 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 15:23 Alex Shi
2011-07-29 15:40 ` Mel Gorman
2011-08-01 0:45 ` Alex,Shi
2011-08-02 10:22 ` Mel Gorman
2011-08-03 0:49 ` Alex,Shi
2011-07-29 18:21 ` Pádraig Brady [this message]
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=4E32FA3D.5060100@draigBrady.com \
--to=p@draigbrady.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=andrea@cpushare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@mit.edu \
--cc=mgorman@suse.de \
--cc=riel@redhat.com \
--cc=shaohua.li@intel.com \
--cc=tim.c.chen@intel.com \
/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