From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: <linux-mm@kvack.org>, Mike Kravetz <mike.kravetz@oracle.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] mm, hugetlb: allocation API and migration improvements
Date: Wed, 3 Jan 2018 16:05:23 -0800 [thread overview]
Message-ID: <20180103160523.2232e3c2da1728c84b160d56@linux-foundation.org> (raw)
In-Reply-To: <20180103093213.26329-1-mhocko@kernel.org>
On Wed, 3 Jan 2018 10:32:07 +0100 Michal Hocko <mhocko@kernel.org> wrote:
> I've posted this as an RFC [1] and both Mike and Naoya seem to be OK
> both with patches and the approach. I have rebased this on top of [2]
> because there is a small conflict in mm/mempolicy.c. I know it is late
> in the release cycle but similarly to [2] I would really like to see
> this in linux-next for a longer time for a wider testing exposure.
I'm interpreting this to mean "hold for 4.17-rc1"?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-mm@kvack.org, Mike Kravetz <mike.kravetz@oracle.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/6] mm, hugetlb: allocation API and migration improvements
Date: Wed, 3 Jan 2018 16:05:23 -0800 [thread overview]
Message-ID: <20180103160523.2232e3c2da1728c84b160d56@linux-foundation.org> (raw)
In-Reply-To: <20180103093213.26329-1-mhocko@kernel.org>
On Wed, 3 Jan 2018 10:32:07 +0100 Michal Hocko <mhocko@kernel.org> wrote:
> I've posted this as an RFC [1] and both Mike and Naoya seem to be OK
> both with patches and the approach. I have rebased this on top of [2]
> because there is a small conflict in mm/mempolicy.c. I know it is late
> in the release cycle but similarly to [2] I would really like to see
> this in linux-next for a longer time for a wider testing exposure.
I'm interpreting this to mean "hold for 4.17-rc1"?
--
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:[~2018-01-04 0:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 9:32 [PATCH 0/6] mm, hugetlb: allocation API and migration improvements Michal Hocko
2018-01-03 9:32 ` Michal Hocko
2018-01-03 9:32 ` [PATCH 1/6] mm, hugetlb: unify core page allocation accounting and initialization Michal Hocko
2018-01-03 9:32 ` Michal Hocko
2018-01-03 9:32 ` [PATCH 2/6] mm, hugetlb: integrate giga hugetlb more naturally to the allocation path Michal Hocko
2018-01-03 9:32 ` Michal Hocko
2018-01-03 9:32 ` [PATCH 3/6] mm, hugetlb: do not rely on overcommit limit during migration Michal Hocko
2018-01-03 9:32 ` Michal Hocko
2018-01-03 9:32 ` [PATCH 4/6] mm, hugetlb: get rid of surplus page accounting tricks Michal Hocko
2018-01-03 9:32 ` Michal Hocko
2018-01-03 9:32 ` [PATCH 5/6] mm, hugetlb: further simplify hugetlb allocation API Michal Hocko
2018-01-03 9:32 ` Michal Hocko
2018-02-21 4:24 ` Dan Rue
2018-02-21 4:24 ` Dan Rue
2018-02-21 9:55 ` Michal Hocko
2018-02-21 9:55 ` Michal Hocko
2018-02-21 10:01 ` Michal Hocko
2018-02-21 10:01 ` Michal Hocko
2018-02-21 16:19 ` Dan Rue
2018-02-21 16:19 ` Dan Rue
2018-02-21 18:52 ` Michal Hocko
2018-02-21 18:52 ` Michal Hocko
2018-02-21 19:05 ` Dan Rue
2018-02-21 19:05 ` Dan Rue
2018-02-21 17:59 ` Mike Kravetz
2018-02-21 17:59 ` Mike Kravetz
2018-02-21 18:54 ` Michal Hocko
2018-02-21 18:54 ` Michal Hocko
2018-02-21 19:14 ` [PATCH] hugetlb: fix surplus pages accounting Michal Hocko
2018-02-21 19:14 ` Michal Hocko
2018-01-03 9:32 ` [PATCH 6/6] hugetlb, mempolicy: fix the mbind hugetlb migration Michal Hocko
2018-01-03 9:32 ` Michal Hocko
2018-01-04 0:05 ` Andrew Morton [this message]
2018-01-04 0:05 ` [PATCH 0/6] mm, hugetlb: allocation API and migration improvements Andrew Morton
2018-01-04 7:32 ` Michal Hocko
2018-01-04 7:32 ` 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=20180103160523.2232e3c2da1728c84b160d56@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.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 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.