From: Michal Hocko <mhocko@suse.cz>
To: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] mm: exclude memory less nodes from zone_reclaim
Date: Wed, 19 Feb 2014 20:40:39 +0100 [thread overview]
Message-ID: <20140219194039.GA5825@dhcp22.suse.cz> (raw)
In-Reply-To: <20140219174940.GF27108@linux.vnet.ibm.com>
On Wed 19-02-14 09:49:41, Nishanth Aravamudan wrote:
> On 19.02.2014 [18:32:59 +0100], Michal Hocko wrote:
> > On Wed 19-02-14 09:16:28, Nishanth Aravamudan wrote:
[...]
> > > I don't think this will work, because what sets N_HIGH_MEMORY (and
> > > shouldn't it be N_MEMORY?)
> >
> > This should be the same thing AFAIU.
>
> I don't think they are guaranteed to be? And, in any case, semantically,
> we care if a node has MEMORY, not if it has HIGH_MEMORY?
I don't know. The whole MEMORY vs HIGH_MEMORY thing is really
confusing. But my understanding was that HIGH_MEMORY is superset of the
other one. But now that I look at the code again it seems that N_MEMORY
is the right thing to use here. I will repost the patch tomorrow if
other parts are good.
[...]
--
Michal Hocko
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-02-19 19:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 9:06 ppc: RECLAIM_DISTANCE 10? Michal Hocko
2014-02-18 22:27 ` David Rientjes
2014-02-19 8:16 ` Michal Hocko
2014-02-19 8:20 ` David Rientjes
2014-02-19 9:19 ` Michal Hocko
2014-02-19 21:45 ` David Rientjes
2014-02-18 23:34 ` Nishanth Aravamudan
2014-02-18 23:58 ` Nishanth Aravamudan
2014-02-19 0:40 ` Nishanth Aravamudan
2014-02-19 1:43 ` David Rientjes
2014-02-19 8:33 ` Michal Hocko
2014-02-19 16:24 ` Nishanth Aravamudan
2014-02-19 16:33 ` Nishanth Aravamudan
2014-02-20 9:55 ` Michal Hocko
2014-02-19 8:23 ` Michal Hocko
2014-02-19 16:26 ` Nishanth Aravamudan
2014-02-19 17:03 ` [RFC PATCH] mm: exclude memory less nodes from zone_reclaim Michal Hocko
2014-02-19 17:16 ` Nishanth Aravamudan
2014-02-19 17:32 ` Michal Hocko
2014-02-19 17:49 ` Nishanth Aravamudan
2014-02-19 19:40 ` Michal Hocko [this message]
2014-02-19 17:53 ` Nishanth Aravamudan
2014-02-19 21:56 ` David Rientjes
2014-02-19 23:05 ` Nishanth Aravamudan
2014-02-20 9:50 ` Michal Hocko
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=20140219194039.GA5825@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nacc@linux.vnet.ibm.com \
--cc=rientjes@google.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).