From: Mel Gorman <mgorman@suse.de>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: minchan.kim@gmail.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, cl@linux.com
Subject: Re: [PATCH 1/3] mm: vmscan: Do use use PF_SWAPWRITE from zone_reclaim
Date: Tue, 12 Jul 2011 11:14:00 +0100 [thread overview]
Message-ID: <20110712101400.GC7529@suse.de> (raw)
In-Reply-To: <4E1C1684.4090706@jp.fujitsu.com>
On Tue, Jul 12, 2011 at 06:40:20PM +0900, KOSAKI Motohiro wrote:
> (2011/07/12 18:27), Minchan Kim wrote:
> > Hi Mel,
> >
> > On Mon, Jul 11, 2011 at 10:01 PM, Mel Gorman <mgorman@suse.de> wrote:
> >> Zone reclaim is similar to direct reclaim in a number of respects.
> >> PF_SWAPWRITE is used by kswapd to avoid a write-congestion check
> >> but it's set also set for zone_reclaim which is inappropriate.
> >> Setting it potentially allows zone_reclaim users to cause large IO
> >> stalls which is worse than remote memory accesses.
> >
> > As I read zone_reclaim_mode in vm.txt, I think it's intentional.
> > It has meaning of throttle the process which are writing large amounts
> > of data. The point is to prevent use of remote node's free memory.
> >
> > And we has still the comment. If you're right, you should remove comment.
> > " * and we also need to be able to write out pages for RECLAIM_WRITE
> > * and RECLAIM_SWAP."
> >
> >
> > And at least, we should Cc Christoph and KOSAKI.
>
> Of course, I'll take full ack this. Do you remember I posted the same patch
> about one year ago.
Nope, I didn't remember it at all :) . I'll revive your signed-off
and sorry about that.
> At that time, Mel disagreed me and I'm glad to see he changed
> the mind. :)
>
Did I disagree because of this?
Simply that I believe the intention of PF_SWAPWRITE here was
to allow zone_reclaim() to aggressively reclaim memory if the
reclaim_mode allowed it as it was a statement that off-node
accesses are really not desired.
Or was some other problem brought up that I'm not thinking of now?
I'm no longer think the level of aggression is appropriate after seeing
how seeing how zone_reclaim can stall when just copying large amounts
of data on recent x86-64 NUMA machines. In the same mail, I said
Ok. I am not fully convinced but I'll not block it either if
believe it's necessary. My current understanding is that this
patch only makes a difference if the server is IO congested in
which case the system is struggling anyway and an off-node
access is going to be relatively small penalty overall.
Conceivably, having PF_SWAPWRITE set makes things worse in
that situation and the patch makes some sense.
While I still think this situation is hard to trigger, zone_reclaim
can cause significant stalls *without* IO and there is little point
making the situation even worse.
--
Mel Gorman
SUSE Labs
--
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>
next prev parent reply other threads:[~2011-07-12 10:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 13:01 [RFC PATCH 0/3] Reduce frequency of stalls due to zone_reclaim() on NUMA Mel Gorman
2011-07-11 13:01 ` [PATCH 1/3] mm: vmscan: Do use use PF_SWAPWRITE from zone_reclaim Mel Gorman
2011-07-12 9:27 ` Minchan Kim
2011-07-12 9:40 ` KOSAKI Motohiro
2011-07-12 9:55 ` Minchan Kim
2011-07-12 15:43 ` Christoph Lameter
2011-07-13 10:40 ` Mel Gorman
2011-07-12 10:14 ` Mel Gorman [this message]
2011-07-13 0:34 ` KOSAKI Motohiro
2011-07-11 13:01 ` [PATCH 2/3] mm: page allocator: Initialise ZLC for first zone eligible for zone_reclaim Mel Gorman
2011-07-13 1:15 ` KOSAKI Motohiro
2011-07-13 11:02 ` Mel Gorman
2011-07-14 1:20 ` KOSAKI Motohiro
2011-07-14 6:11 ` Mel Gorman
2011-07-11 13:01 ` [PATCH 3/3] mm: page allocator: Reconsider zones for allocation after direct reclaim Mel Gorman
2011-07-13 0:42 ` KOSAKI Motohiro
2011-07-13 11:10 ` Mel Gorman
2011-07-14 3:20 ` KOSAKI Motohiro
2011-07-14 6:10 ` Mel Gorman
2011-07-21 9:35 ` KOSAKI Motohiro
2011-07-21 10:31 ` Mel Gorman
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=20110712101400.GC7529@suse.de \
--to=mgorman@suse.de \
--cc=cl@linux.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.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;
as well as URLs for NNTP newsgroup(s).