From: Hanjun Guo <guohanjun@huawei.com>
To: Christoph Lameter <cl@linux.com>
Cc: Wu Jianguo <wujianguo@huawei.com>,
Jiang Liu <jiang.liu@huawei.com>, Tony Luck <tony.luck@intel.com>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
Mel Gorman <mgorman@suse.de>, Yinghai Lu <yinghai@kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
David Rientjes <rientjes@google.com>,
Minchan Kim <minchan@kernel.org>,
Keping Chen <chenkeping@huawei.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Jiang Liu <liuj97@gmail.com>
Subject: Re: [RFC PATCH] mm: introduce N_LRU_MEMORY to distinguish between normal and movable memory
Date: Thu, 16 Aug 2012 16:19:49 +0800 [thread overview]
Message-ID: <502CAD25.7060201@huawei.com> (raw)
In-Reply-To: <00000139257cb4f7-55034aa0-7541-498a-9a3f-259435ccec65-000000@email.amazonses.com>
On 2012/8/14 22:14, Christoph Lameter wrote:
> On Tue, 14 Aug 2012, Hanjun Guo wrote:
>
>> N_NORMAL_MEMORY means !LRU allocs possible.
>
> Ok. I am fine with that change. However this is a significant change that
> needs to be mentioned prominently in the changelog and there need to be
> some comments explaining the meaning of these flags clearly in the source.
No problem, we will handle it in next version of this patch.
Thanks
Hanjun Guo
>
>
> .
>
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Hanjun Guo <guohanjun@huawei.com>
To: Christoph Lameter <cl@linux.com>
Cc: Wu Jianguo <wujianguo@huawei.com>,
Jiang Liu <jiang.liu@huawei.com>, Tony Luck <tony.luck@intel.com>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
Mel Gorman <mgorman@suse.de>, Yinghai Lu <yinghai@kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
David Rientjes <rientjes@google.com>,
Minchan Kim <minchan@kernel.org>,
Keping Chen <chenkeping@huawei.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, Jiang Liu <liuj97@gmail.com>
Subject: Re: [RFC PATCH] mm: introduce N_LRU_MEMORY to distinguish between normal and movable memory
Date: Thu, 16 Aug 2012 16:19:49 +0800 [thread overview]
Message-ID: <502CAD25.7060201@huawei.com> (raw)
In-Reply-To: <00000139257cb4f7-55034aa0-7541-498a-9a3f-259435ccec65-000000@email.amazonses.com>
On 2012/8/14 22:14, Christoph Lameter wrote:
> On Tue, 14 Aug 2012, Hanjun Guo wrote:
>
>> N_NORMAL_MEMORY means !LRU allocs possible.
>
> Ok. I am fine with that change. However this is a significant change that
> needs to be mentioned prominently in the changelog and there need to be
> some comments explaining the meaning of these flags clearly in the source.
No problem, we will handle it in next version of this patch.
Thanks
Hanjun Guo
>
>
> .
>
next prev parent reply other threads:[~2012-08-16 8:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1344482788-4984-1-git-send-email-guohanjun@huawei.com>
2012-08-09 4:39 ` [RFC PATCH] mm: introduce N_LRU_MEMORY to distinguish between normal and movable memory Hanjun Guo
2012-08-09 4:39 ` Hanjun Guo
2012-08-09 14:06 ` Christoph Lameter (Open Source)
2012-08-09 14:06 ` Christoph Lameter (Open Source)
2012-08-10 8:48 ` Hanjun Guo
2012-08-10 8:48 ` Hanjun Guo
2012-08-10 14:12 ` Christoph Lameter (Open Source)
2012-08-10 14:12 ` Christoph Lameter (Open Source)
2012-08-14 11:56 ` Hanjun Guo
2012-08-14 11:56 ` Hanjun Guo
2012-08-14 14:14 ` Christoph Lameter
2012-08-14 14:14 ` Christoph Lameter
2012-08-16 8:19 ` Hanjun Guo [this message]
2012-08-16 8:19 ` Hanjun Guo
2012-08-10 9:43 ` Yasuaki Ishimatsu
2012-08-10 9:43 ` Yasuaki Ishimatsu
2012-08-10 12:21 ` Jiang Liu
2012-08-10 12:21 ` Jiang Liu
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=502CAD25.7060201@huawei.com \
--to=guohanjun@huawei.com \
--cc=chenkeping@huawei.com \
--cc=cl@linux.com \
--cc=jiang.liu@huawei.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=tony.luck@intel.com \
--cc=wujianguo@huawei.com \
--cc=yinghai@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.