[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180315195329.7787-1-willy@infradead.org>
Date: Thu, 15 Mar 2018 12:53:27 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Alexander Duyck <alexander.h.duyck@...el.com>
Cc: linux-mm@...r.kernel.org, netdev@...r.kernel.org,
Matthew Wilcox <mawilcox@...rosoft.com>
Subject: [RFC 0/2] Shrink page_frag_cache
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
include/linux/mm.h | 16 ++----
include/linux/mm_types.h | 17 +-----
mm/page_alloc.c | 143 ++++++++++++++++++++++++-----------------------
net/core/skbuff.c | 4 +-
4 files changed, 82 insertions(+), 98 deletions(-)
--
2.16.2
Powered by blists - more mailing lists