[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180613201802.45m2745soztmkxmp@black.fi.intel.com>
Date: Wed, 13 Jun 2018 23:18:02 +0300
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Tom Lendacky <thomas.lendacky@....com>,
Kai Huang <kai.huang@...ux.intel.com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCHv3 02/17] mm/khugepaged: Do not collapse pages in
encrypted VMAs
On Wed, Jun 13, 2018 at 05:50:24PM +0000, Dave Hansen wrote:
> On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> > Pages for encrypted VMAs have to be allocated in a special way:
> > we would need to propagate down not only desired NUMA node but also
> > whether the page is encrypted.
> >
> > It complicates not-so-trivial routine of huge page allocation in
> > khugepaged even more. It also puts more pressure on page allocator:
> > we cannot re-use pages allocated for encrypted VMA to collapse
> > page in unencrypted one or vice versa.
> >
> > I think for now it worth skipping encrypted VMAs. We can return
> > to this topic later.
>
> You're asking for this to be included, but without a major piece of THP
> support. Is THP support unimportant for this feature?
>
> Are we really asking the x86 maintainers to merge this feature with this
> restriction in place?
I gave it more thought after your comment and I think I see a way to get
khugepaged work with memory encryption.
Let me check it tomorrow.
--
Kirill A. Shutemov
Powered by blists - more mailing lists