From: Michal Hocko <mhocko@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, suzuki.poulose@arm.com,
punit.agrawal@arm.com, will.deacon@arm.com, Steven.Price@arm.com,
steve.capper@arm.com, catalin.marinas@arm.com,
akpm@linux-foundation.org, mike.kravetz@oracle.com,
n-horiguchi@ah.jp.nec.com
Subject: Re: [PATCH V2 1/5] mm/hugetlb: Enable PUD level huge page migration
Date: Mon, 22 Oct 2018 09:16:25 +0200 [thread overview]
Message-ID: <20181022071625.GS18839@dhcp22.suse.cz> (raw)
In-Reply-To: <7d32fcdc-1ee3-7666-3b33-eda14ca8b380@arm.com>
On Mon 22-10-18 08:31:05, Anshuman Khandual wrote:
> On 10/19/2018 01:39 PM, Michal Hocko wrote:
> > I would probably fold it into the one which defines arch specific hook.
>
> Hmm but that may be like doing two functionality changes together. Adding one
> more conditional check and at the same time wrapping it over with a new name
> which is part of a new scheme. I would suggest keeping the patches separate.
I will surely not insist. If you think it is better this way then no
objections from me of course.
--
Michal Hocko
SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: mhocko@kernel.org (Michal Hocko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/5] mm/hugetlb: Enable PUD level huge page migration
Date: Mon, 22 Oct 2018 09:16:25 +0200 [thread overview]
Message-ID: <20181022071625.GS18839@dhcp22.suse.cz> (raw)
In-Reply-To: <7d32fcdc-1ee3-7666-3b33-eda14ca8b380@arm.com>
On Mon 22-10-18 08:31:05, Anshuman Khandual wrote:
> On 10/19/2018 01:39 PM, Michal Hocko wrote:
> > I would probably fold it into the one which defines arch specific hook.
>
> Hmm but that may be like doing two functionality changes together. Adding one
> more conditional check and at the same time wrapping it over with a new name
> which is part of a new scheme. I would suggest keeping the patches separate.
I will surely not insist. If you think it is better this way then no
objections from me of course.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-10-22 7:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 3:59 [PATCH V2 0/5] arm64/mm: Enable HugeTLB migration Anshuman Khandual
2018-10-12 3:59 ` Anshuman Khandual
2018-10-12 3:59 ` [PATCH V2 1/5] mm/hugetlb: Enable PUD level huge page migration Anshuman Khandual
2018-10-12 3:59 ` Anshuman Khandual
2018-10-19 8:09 ` Michal Hocko
2018-10-19 8:09 ` Michal Hocko
2018-10-22 3:01 ` Anshuman Khandual
2018-10-22 3:01 ` Anshuman Khandual
2018-10-22 7:16 ` Michal Hocko [this message]
2018-10-22 7:16 ` Michal Hocko
2018-10-12 3:59 ` [PATCH V2 2/5] mm/hugetlb: Distinguish between migratability and movability Anshuman Khandual
2018-10-12 3:59 ` Anshuman Khandual
2018-10-19 1:59 ` Naoya Horiguchi
2018-10-19 1:59 ` Naoya Horiguchi
2018-10-19 1:59 ` Naoya Horiguchi
2018-10-19 2:32 ` Anshuman Khandual
2018-10-19 2:32 ` Anshuman Khandual
2018-10-19 2:32 ` Anshuman Khandual
2018-10-12 3:59 ` [PATCH V2 3/5] mm/hugetlb: Enable arch specific huge page size support for migration Anshuman Khandual
2018-10-12 3:59 ` Anshuman Khandual
2018-10-12 3:59 ` [PATCH V2 4/5] arm64/mm: Enable HugeTLB migration Anshuman Khandual
2018-10-12 3:59 ` Anshuman Khandual
2018-10-12 3:59 ` [PATCH V2 5/5] arm64/mm: Enable HugeTLB migration for contiguous bit HugeTLB pages Anshuman Khandual
2018-10-12 3:59 ` Anshuman Khandual
2018-10-17 8:19 ` [PATCH V2 0/5] arm64/mm: Enable HugeTLB migration Anshuman Khandual
2018-10-17 8:19 ` Anshuman Khandual
2018-10-19 2:01 ` Naoya Horiguchi
2018-10-19 2:01 ` Naoya Horiguchi
2018-10-19 2:01 ` Naoya Horiguchi
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=20181022071625.GS18839@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=Steven.Price@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=punit.agrawal@arm.com \
--cc=steve.capper@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@arm.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.