From: Christoph Hellwig <hch@infradead.org>
To: mchristi@redhat.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, dm-devel@redhat.com,
linux-fsdevel@vger.kernel.org, drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [RESEND RFC PATCH 00/32] separate operations from flags in the bio/request structs
Date: Sat, 7 Nov 2015 02:10:23 -0800 [thread overview]
Message-ID: <20151107101023.GA12117@infradead.org> (raw)
In-Reply-To: <1446674909-5371-1-git-send-email-mchristi@redhat.com>
On Wed, Nov 04, 2015 at 04:07:57PM -0600, mchristi@redhat.com wrote:
> Known issues:
> - REQ_FLUSH is still a flag, but should probably be a operation.
> For lower level drivers like SCSI where we only get a flush, it makes
> more sense to be a operation. However, upper layers like filesystems
> can send down flushes with writes, so it is more of a flag for them.
> I am still working on this.
Actually it should be both. REQ_OP_FLUSH for a real flush operation,
and a REQ_PREFLUSH bio flag that the request layer will sequence into
an actual write an a flush operation.
next prev parent reply other threads:[~2015-11-07 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1446674909-5371-1-git-send-email-mchristi@redhat.com>
[not found] ` <1446674909-5371-20-git-send-email-mchristi@redhat.com>
2015-11-04 22:44 ` [Drbd-dev] [dm-devel] [PATCH 19/32] block: add helper to get data dir from op Bart Van Assche
[not found] ` <563B930F.7040705@redhat.com>
2015-11-07 10:19 ` Christoph Hellwig
2015-11-07 10:10 ` Christoph Hellwig [this message]
[not found] ` <1446674909-5371-7-git-send-email-mchristi@redhat.com>
2015-11-07 10:17 ` [Drbd-dev] [PATCH 06/32] xen blkback: prepare for bi_rw split Christoph Hellwig
[not found] ` <1446674909-5371-33-git-send-email-mchristi@redhat.com>
2015-11-07 10:21 ` [Drbd-dev] [PATCH 32/32] block: remove __REQ op defs and reduce bi_op/bi_rw sizes 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=20151107101023.GA12117@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@redhat.com \
--cc=drbd-dev@lists.linbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mchristi@redhat.com \
/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