[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKgT0Uf96pm-BP6qCbsjkzwkXmSHGDR2KAju=Bbr=ut=J0rFCw@mail.gmail.com>
Date: Thu, 15 Mar 2018 13:02:34 -0700
From: Alexander Duyck <alexander.duyck@...il.com>
To: Matthew Wilcox <willy@...radead.org>,
Jesper Dangaard Brouer <brouer@...hat.com>
Cc: Alexander Duyck <alexander.h.duyck@...el.com>,
linux-mm@...r.kernel.org, Netdev <netdev@...r.kernel.org>,
Matthew Wilcox <mawilcox@...rosoft.com>
Subject: Re: [RFC 0/2] Shrink page_frag_cache
On Thu, Mar 15, 2018 at 12:53 PM, Matthew Wilcox <willy@...radead.org> wrote:
> From: Matthew Wilcox <mawilcox@...rosoft.com>
>
> I've just learned about the page_frag_cache allocator, and now I want
> to use it everywhere ;-)
>
> But before I start using it in other places, I want to see if it can
> be improved at all. The pfmemalloc flag is pretty specific to how the
> network stack uses it (with GFP_ATOMIC), and the pagecnt_bias is tricky
> to understand. I think we can do better by just using the fields in
> struct page directly. I don't have a suitable setup for performance
> testing this code ... Alex, is there any chance you'd have time to give
> this a spin?
>
> Matthew Wilcox (2):
> mm: Use page->mapping to indicate pfmemalloc
> page_frag_cache: Store metadata in struct page
I can try taking a look at it, but I am pretty swamped for the next
several days. I probably won't have any free time to really test
something like this until Monday or Tuesday of next week. I've added
Jesper to the Cc as this might be something he is interested in as
well.
Thanks.
- Alex
Powered by blists - more mailing lists