On Tue, Jan 14, 2014 at 10:00:51AM -0800, Dave Hansen wrote:
>
> From: Dave Hansen
>
> page->pfmemalloc does not deserve a spot in 'struct page'. It is
> only used transiently _just_ after a page leaves the buddy
> allocator.
>
> Instead of declaring a union, we move its functionality behind a
On Tue, 14 Jan 2014, Dave Hansen wrote:
> >> page->pfmemalloc does not deserve a spot in 'struct page'. It is
> >> only used transiently _just_ after a page leaves the buddy
> >> allocator.
> >
> > Why would we need to do this if we are removing the cmpxchg_double?
>
> Why do we need the patch?
On 01/14/2014 11:49 AM, Christoph Lameter wrote:
> On Tue, 14 Jan 2014, Dave Hansen wrote:
>> page->pfmemalloc does not deserve a spot in 'struct page'. It is
>> only used transiently _just_ after a page leaves the buddy
>> allocator.
>
> Why would we need to do this if we are removing the cmpxch
On Tue, 14 Jan 2014, Dave Hansen wrote:
> page->pfmemalloc does not deserve a spot in 'struct page'. It is
> only used transiently _just_ after a page leaves the buddy
> allocator.
Why would we need to do this if we are removing the cmpxchg_double?
--
To unsubscribe from this list: send the line
From: Dave Hansen
page->pfmemalloc does not deserve a spot in 'struct page'. It is
only used transiently _just_ after a page leaves the buddy
allocator.
Instead of declaring a union, we move its functionality behind a
few quick accessor functions. This way we could also much more
easily audit
5 matches
Mail list logo