From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vlastimil Babka Subject: Re: [RFC PATCH 3/3] mm, proc: report PR_SET_THP_DISABLE in proc Date: Tue, 27 Nov 2018 17:50:24 +0100 Message-ID: <283f38d9-1142-60b6-0b84-7129b7f9781e@suse.cz> References: <20181120103515.25280-1-mhocko@kernel.org> <20181120103515.25280-4-mhocko@kernel.org> <0ACDD94B-75AD-4DD0-B2E3-32C0EDFBAA5E@oracle.com> <20181127131707.GW12455@dhcp22.suse.cz> <04647F77-FE93-4A8E-90C1-4245709B88A5@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <04647F77-FE93-4A8E-90C1-4245709B88A5@oracle.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: William Kucharski , Michal Hocko Cc: linux-api@vger.kernel.org, Andrew Morton , Alexey Dobriyan , linux-mm@kvack.org, LKML List-Id: linux-api@vger.kernel.org On 11/27/18 3:50 PM, William Kucharski wrote: > > I was just double checking that this was meant to be more of a check done > before code elsewhere performs additional checks and does the actual THP > mapping, not an all-encompassing go/no go check for THP mapping. Yes, the code doing the actual mapping is still checking also alignment etc.