[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <85f6cdc2-e801-2def-def8-112be862b3a7@intel.com>
Date: Tue, 19 Jun 2018 10:06:58 -0700
From: Reinette Chatre <reinette.chatre@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: fenghua.yu@...el.com, tony.luck@...el.com,
vikas.shivappa@...ux.intel.com, gavin.hindman@...el.com,
jithu.joseph@...el.com, dave.hansen@...el.com, mingo@...hat.com,
hpa@...or.com, x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V5 00/38] Intel(R) Resource Director Technology Cache
Pseudo-Locking enabling
Hi Thomas,
On 6/19/2018 9:57 AM, Thomas Gleixner wrote:
> On Tue, 29 May 2018, Reinette Chatre wrote:
>>
>> The last patch of this series depends on the series:
>> "[RFC PATCH 0/3] Interface for higher order contiguous allocations"
>> submitted at:
>> http://lkml.kernel.org/r/20180212222056.9735-1-mike.kravetz@oracle.com
>> A new version of this was submitted recently and currently being discussed
>> at:
>> http://lkml.kernel.org/r/20180417020915.11786-1-mike.kravetz@oracle.com
>> Without this upstream MM work (and patch 39/39 of this series) it would
>
> There are only 38 patches and none which might depend on Mikes work :)
I am sorry for adding confusion by keeping the changelog from previous
versions with each new submission. v3 had 39 patches with the last patch
depending on Mike's work. I removed that final patch in v4, planning to
resubmit it when Mike's work has been merged since it seems the API I
used may change.
> So the whole thing is self contained and just limited to 4MB, right?
Correct.
Reinette
Powered by blists - more mailing lists