From: Christoph Hellwig <hch@lst.de>
To: ming.lei@redhat.com
Cc: linux-block@vger.kernel.org
Subject: ublk vs write cache and FUA
Date: Thu, 21 Jul 2022 17:14:58 +0200 [thread overview]
Message-ID: <20220721151458.GA4399@lst.de> (raw)
Hi Ming,
ublk implements REQ_OP_FLUSH and REQ_FUA, but will never see those as
it never calls blk_queue_write_cache. Can we drop the code? Or should
there be a flag to enable write cache and fua support when setting up
a device?
next reply other threads:[~2022-07-21 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 15:14 Christoph Hellwig [this message]
2022-07-21 15:27 ` ublk vs write cache and FUA Ming Lei
2022-07-22 9:06 ` Ming Lei
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=20220721151458.GA4399@lst.de \
--to=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@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 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.