From: Christopher Lameter <cl@linux.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Dave Chinner <david@fromorbit.com>,
Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: How can we share page cache pages for reflinked files?
Date: Tue, 15 Aug 2017 10:11:22 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1708151009440.8223@nuc-kabylake> (raw)
In-Reply-To: <20170814210959.r4mdv3y4rdeolyxt@node.shutemov.name>
On Tue, 15 Aug 2017, Kirill A. Shutemov wrote:
> > This would also allow the inevitable creeping page struct bloat to get
> > completely out of control.
>
> Nice wish list. Add pony. :)
>
> Any attempt to replace struct page with something more complex will have
> severe performance implications. I'll be glad proved otherwise.
Do we care that much anymore? I have people inserting all sorts of runtime
checks into hotpaths in the name of security.....
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-08-15 15:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 4:28 Dave Chinner
2017-08-10 5:57 ` Kirill A. Shutemov
2017-08-10 9:01 ` Dave Chinner
2017-08-10 13:31 ` Kirill A. Shutemov
2017-08-11 3:59 ` Dave Chinner
2017-08-11 12:57 ` Kirill A. Shutemov
2017-08-10 16:11 ` Matthew Wilcox
2017-08-10 19:17 ` Vivek Goyal
2017-08-10 21:20 ` Matthew Wilcox
2017-08-11 4:25 ` Dave Chinner
2017-08-11 17:08 ` Matthew Wilcox
2017-08-11 18:04 ` Christoph Hellwig
2017-08-14 6:48 ` Dave Chinner
2017-08-14 18:14 ` Christopher Lameter
2017-08-14 21:09 ` Kirill A. Shutemov
2017-08-15 15:11 ` Christopher Lameter [this message]
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=alpine.DEB.2.20.1708151009440.8223@nuc-kabylake \
--to=cl@linux.com \
--cc=david@fromorbit.com \
--cc=kirill@shutemov.name \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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