netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Alexander Duyck <alexander.h.duyck@intel.com>
Cc: linux-mm@vger.kernel.org, netdev@vger.kernel.org,
	Matthew Wilcox <mawilcox@microsoft.com>
Subject: [RFC 0/2] Shrink page_frag_cache
Date: Thu, 15 Mar 2018 12:53:27 -0700	[thread overview]
Message-ID: <20180315195329.7787-1-willy@infradead.org> (raw)

From: Matthew Wilcox <mawilcox@microsoft.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

             reply	other threads:[~2018-03-15 19:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 19:53 Matthew Wilcox [this message]
2018-03-15 19:53 ` [RFC 1/2] mm: Use page->mapping to indicate pfmemalloc Matthew Wilcox
2018-03-15 19:53 ` [RFC 2/2] page_frag_cache: Store metadata in struct page Matthew Wilcox
2018-03-15 21:03   ` Eric Dumazet
2018-03-15 21:26   ` Alexander Duyck
2018-03-16 21:05     ` Matthew Wilcox
2018-03-16 21:32       ` Eric Dumazet
2018-03-19  8:27       ` Jesper Dangaard Brouer
2018-03-17 20:54     ` David Miller
2018-03-17  2:17   ` [page_frag_cache] 47b0eaa4b5: BUG:unable_to_handle_kernel kernel test robot
2018-03-20 20:47   ` [RFC 2/2] page_frag_cache: Store metadata in struct page Alexander Duyck
2018-03-15 20:02 ` [RFC 0/2] Shrink page_frag_cache Alexander Duyck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180315195329.7787-1-willy@infradead.org \
    --to=willy@infradead.org \
    --cc=alexander.h.duyck@intel.com \
    --cc=linux-mm@vger.kernel.org \
    --cc=mawilcox@microsoft.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).