From: Steven Whitehouse <swhiteho@redhat.com>
To: scameron@beardog.cce.hp.com
Cc: linux-kernel@vger.kernel.org, jens.axboe@kernel.dk, tj@kernel.org
Subject: Re: Question about REQ_FLUSH and bios with data
Date: Fri, 09 Aug 2013 21:18:15 +0100 [thread overview]
Message-ID: <1376079495.2718.15.camel@menhir> (raw)
In-Reply-To: <20130809190934.GL9905@beardog.cce.hp.com>
Hi,
On Fri, 2013-08-09 at 14:09 -0500, scameron@beardog.cce.hp.com wrote:
> So, I'm working on a block driver using the make_request_fn
> interface, and have to handle a bio that comes in with
> (bi_rw & REQ_FLUSH) set AND data to transfer.
>
> According to Documentation/block/writeback_cache_control.txt:
>
> The REQ_FLUSH flag can be OR ed into the r/w flags of a
> bio submitted from the filesystem and will make sure the
> volatile cache of the storage device has been flushed
> before the actual I/O operation is started.
>
> So I've written code that handles that case, along with the
> various error cases I might encounter, I think, which leads
> to my question:
>
> How do I get such a bio with a data transfer AND the REQ_FLUSH bit
> set to come into the driver? Just wondering how to test this case.
>
GFS2 does this... if you look at the log flush code and the function
log_write_header() in particular, you'll see that it sets this on each
log header that gets written. You don't need a cluster to generate this
kind of i/o, just supply mkfs.gfs2 with -p lock_nolock and mount it as a
local filesystem. The combination of touch foo; sync should be enough to
generate a log flush writing a log header with this flag set,
Steve.
> Thanks,
>
> (I cc'ed Tejun Heo just because his name is in block/blk-flush.c)
>
> -- steve
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2013-08-09 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 19:09 scameron
2013-08-09 19:11 ` scameron
2013-08-09 20:18 ` Steven Whitehouse [this message]
2013-08-09 20:34 ` scameron
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=1376079495.2718.15.camel@menhir \
--to=swhiteho@redhat.com \
--cc=jens.axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=scameron@beardog.cce.hp.com \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®