[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140411130027.GA15758@quack.suse.cz>
Date: Fri, 11 Apr 2014 15:00:27 +0200
From: Jan Kara <jack@...e.cz>
To: Christoph Hellwig <hch@...radead.org>
Cc: Fabian Frederick <fabf@...net.be>, Viro <viro@...iv.linux.org.uk>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
jack <jack@...e.cz>, akpm <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/1] FS: Add generic data flush to fsync
On Fri 11-04-14 00:45:22, Christoph Hellwig wrote:
> On Fri, Apr 11, 2014 at 06:52:42AM +0200, Fabian Frederick wrote:
> > Currently, there's no generic HW flush management support in kernel.
> > Only 7 filesystems have their own way to manage the barrier flag.
> >
> > This patch adds MS_BARRIER in sb_flags and conditionnaly issues the flush
> > in generic_file_fsync.
>
> Please don't add a binary mount option for something thast already is a
> text option in many filesystems. We can actually enable/disable cache
> flushes at the block device level, so I think this can be
> unconditional.
How can those be disabled? I didn't find that by a quick look through
/sys and flush code in kernel...
Honza
--
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists