> > The idea is simple, leave the desicion for the file system user to enable
> > file system mount
> > wide O_DIRECT support with a new mount option, for example,
> I believe a better approach to your problem is actually to enable
> loopback device driver to use direct IO. Someone was actuall
On Tue, Sep 04, 2012 at 06:57:14AM -0400, Christoph Hellwig wrote:
> 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 t
On Tue 04-09-12 18:17:47, 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.
> In many cases, it is beneficial to turn on the O_DIRECT option while
> performing
> the upper fil
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
For file system created on file-backed loop device, there will be two-levels of
page cache present, which typically doubles the memory consumption.
In many cases, it is beneficial to turn on the O_DIRECT option while performing
the upper file system file IO, to bypass the upper page cache, which
5 matches
Mail list logo
