From: Christoph Hellwig <hch@infradead.org>
To: Li Wang <liwang@nudt.edu.cn>
Cc: viro@zeniv.linux.org.uk, axboe@kernel.dk,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] VFS: File System Mount Wide O_DIRECT Support
Date: Tue, 4 Sep 2012 06:57:14 -0400 [thread overview]
Message-ID: <20120904105714.GA31020@infradead.org> (raw)
In-Reply-To: <000001cd8a86$89df83b0$9d9e8b10$@edu.cn>
On Tue, Sep 04, 2012 at 06:17:47PM +0800, Li Wang wrote:
> For file system created on file-backed loop device, there will be two-levels of
> page cache present, which typically doubles the memory consumption.
And the right fix is to not use buffer I/O on the backing file instead
of hacks like this.
next prev parent reply other threads:[~2012-09-04 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 10:17 [RFC] VFS: File System Mount Wide O_DIRECT Support Li Wang
2012-09-04 10:57 ` Christoph Hellwig [this message]
2012-09-04 14:09 ` Matthew Wilcox
2012-09-04 12:27 ` Jan Kara
2012-09-04 23:28 ` Zach Brown
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=20120904105714.GA31020@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwang@nudt.edu.cn \
--cc=viro@zeniv.linux.org.uk \
/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).