From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 4/4] ext4: Add fdatasync scalability optimization
Date: Tue, 14 Oct 2014 15:25:54 +0400 [thread overview]
Message-ID: <87oateq4e5.fsf@openvz.org> (raw)
In-Reply-To: <20141014105729.GA19981@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
Christoph Hellwig <hch@infradead.org> writes:
> 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.
[-- Attachment #2: Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2014-10-14 11:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 10:03 [PATCH 0/4] blkdev: flush optimization Dmitry Monakhov
2014-10-14 10:03 ` [PATCH 1/4] blkdev: add flush generation counter Dmitry Monakhov
2014-10-16 14:24 ` Ming Lei
2014-10-16 15:14 ` Dmitry Monakhov
2014-10-18 9:59 ` Ming Lei
2014-10-18 11:52 ` Dmitry Monakhov
2014-10-14 10:03 ` [PATCH 2/4] md: add flush_idx support for stacked devices Dmitry Monakhov
2014-10-14 12:25 ` Mike Snitzer
2014-10-14 10:03 ` [PATCH 3/4] ext4: cleanup data integrity sync fo nonjournal mode Dmitry Monakhov
2014-10-14 10:03 ` [PATCH 4/4] ext4: Add fdatasync scalability optimization Dmitry Monakhov
2014-10-14 10:57 ` Christoph Hellwig
2014-10-14 11:25 ` Dmitry Monakhov [this message]
2014-10-14 11:35 ` Christoph Hellwig
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=87oateq4e5.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.