From: David Rientjes <rientjes@google.com>
To: Jianyu Zhan <nasa4836@gmail.com>
Cc: akpm@linux-foundation.org, mgorman@suse.de, riel@redhat.com,
sasha.levin@oracle.com, n-horiguchi@ah.jp.nec.com,
andriy.shevchenko@linux.intel.com, hannes@cmpxchg.org,
vdavydov@parallels.com, fabf@skynet.be, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Jianyu Zhan <jianyu.zhan@emc.com>
Subject: Re: [PATCH] mm, gfp: escalatedly define GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE
Date: Mon, 24 Nov 2014 13:34:33 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1411241334210.21237@chino.kir.corp.google.com> (raw)
In-Reply-To: <1416847427-2550-1-git-send-email-nasa4836@gmail.com>
On Tue, 25 Nov 2014, Jianyu Zhan wrote:
> GFP_USER, GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE are escalatedly
> confined defined, also implied by their names:
>
> GFP_USER = GFP_USER
> GFP_USER + __GFP_HIGHMEM = GFP_HIGHUSER
> GFP_USER + __GFP_HIGHMEM + __GFP_MOVABLE = GFP_HIGHUSER_MOVABLE
>
> So just make GFP_HIGHUSER and GFP_HIGHUSER_MOVABLE escalatedly defined
> to reflect this fact. It also makes the definition clear and texturally
> warn on any furture break-up of this escalated relastionship.
>
> Signed-off-by: Jianyu Zhan <jianyu.zhan@emc.com>
Acked-by: David Rientjes <rientjes@google.com>
--
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>
prev parent reply other threads:[~2014-11-24 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 16:43 Jianyu Zhan
2014-11-24 18:21 ` Johannes Weiner
2014-11-24 19:01 ` Kirill A. Shutemov
2014-11-24 21:35 ` David Rientjes
2014-11-25 14:32 ` Kirill A. Shutemov
2014-11-24 21:34 ` David Rientjes [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=alpine.DEB.2.10.1411241334210.21237@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fabf@skynet.be \
--cc=hannes@cmpxchg.org \
--cc=jianyu.zhan@emc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=nasa4836@gmail.com \
--cc=riel@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=vdavydov@parallels.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