From: Xishi Qiu <qiuxishi@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
David Rientjes <rientjes@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v3] mem-hotplug: alloc new page from a nearest neighbor node when mem-offline
Date: Tue, 26 Jul 2016 09:36:02 +0800 [thread overview]
Message-ID: <5796BE82.4060903@huawei.com> (raw)
In-Reply-To: <20160725135159.d8f06042d91a5b5d1e5c4ebf@linux-foundation.org>
On 2016/7/26 4:51, Andrew Morton wrote:
> On Mon, 25 Jul 2016 17:53:15 +0800 Xishi Qiu <qiuxishi@huawei.com> wrote:
>
>> Subject: [PATCH v3] mem-hotplug: alloc new page from a nearest neighbor node when mem-offline
>
> argh.
>
> This is "v3" but there is no v1 and no v2. Please don't change the
> name of patches in this manner. Or if you do, please be clear which
> patch is being updated.
>
> I'll drop your
> mem-hotplug-use-different-mempolicy-in-alloc_migrate_target.patch.
>
Hi Andrew,
Sorry for the confusion of title.
The following patches are all the old versions and please drop them all.
[PATCH] mem-hotplug: use GFP_HIGHUSER_MOVABLE and alloc from next node in alloc_migrate_target()
[PATCH 1/2] mem-hotplug: use GFP_HIGHUSER_MOVABLE in, alloc_migrate_target()
[PATCH 2/2] mem-hotplug: use different mempolicy in alloc_migrate_target()
[PATCH v2] mem-hotplug: alloc new page from the next node if zone is MOVABLE_ZONE
Thanks,
Xishi Qiu
> .
>
--
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:[~2016-07-26 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 9:53 [PATCH v3] mem-hotplug: alloc new page from a nearest neighbor node when mem-offline Xishi Qiu
2016-07-25 20:51 ` Andrew Morton
2016-07-26 1:36 ` Xishi Qiu [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=5796BE82.4060903@huawei.com \
--to=qiuxishi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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).