From: David Miller <davem@davemloft.net>
To: alexander.duyck@gmail.com
Cc: willy@infradead.org, alexander.h.duyck@intel.com,
linux-mm@vger.kernel.org, netdev@vger.kernel.org,
mawilcox@microsoft.com
Subject: Re: [RFC 2/2] page_frag_cache: Store metadata in struct page
Date: Sat, 17 Mar 2018 16:54:58 -0400 (EDT) [thread overview]
Message-ID: <20180317.165458.1452469008226572576.davem@davemloft.net> (raw)
In-Reply-To: <CAKgT0Uf0qWbo7T8j00Owt_hEj6vZSY-MOsqUeZCek1x62DKz4Q@mail.gmail.com>
From: Alexander Duyck <alexander.duyck@gmail.com>
Date: Thu, 15 Mar 2018 14:26:28 -0700
> So my concern with this patch is that it is essentially trading off
> CPU performance for reduced size. One of the reasons for getting away
> from using the page pointer is because it is expensive to access the
> page when the ref_count is bouncing on multiple cache lines.
Agreed.
next prev parent reply other threads:[~2018-03-17 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 19:53 [RFC 0/2] Shrink page_frag_cache Matthew Wilcox
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 [this message]
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=20180317.165458.1452469008226572576.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=linux-mm@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=willy@infradead.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).