Messages in this thread | | | Date | Fri, 27 May 2011 16:27:47 -0400 | From | Christoph Hellwig <> | Subject | Re: [PATCH 1/2] blktrace: treat flush as barrier |
| |
On Fri, May 27, 2011 at 10:17:09PM +0200, Jens Axboe wrote: > Agree on Christophs comments, we should not pretend they are the same > (since they are not). Since flush is a request on its own, F works > nicely. For FUA it's associated with a write, so F should work there too > indicating Write Fua (and easily humanly parsed as that, or Write > Flush). WU would look confusing.
REQ_FLUSH can also be set on a write bio, it only gets split at the request level. And even there we're at least pondering allowing it to stay as part of the write for some paravirtualized storage protocols.
| |