Thread (4 messages) 4 messages, 2 authors, 2014-10-14

Re: [PATCH 4/4] ext4: Add fdatasync scalability optimization

From: Christoph Hellwig <hch@infradead.org>
Date: 2014-10-14 11:35:47
Also in: linux-fsdevel, lkml

On Tue, Oct 14, 2014 at 03:25:54PM +0400, Dmitry Monakhov wrote:
Christoph Hellwig [off-list ref] writes:
quoted
Much of the bookkeeping here seems generic and should be in common
code and not inside a filesystem.
Yes. But this means that I need to store flush_id inside generic inode
which likely will be accepted negatively because VFS people do not like
inode bloating. But if you are OK then I'll prepare the patch.
With my "VFS person critical of struct inode size increases" hat on
I'm still critical of any struct inode increase, so if you can find
an option that say just takes the address of the counter variable
I'd prefer that.  But even if we have to increase the inode this might
be one of the cases where it's fine as cache flushing is something
at least all on disk filesystems need to do.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help