From: Mike Snitzer <snitzer@redhat.com>
To: linux-block@vger.kernel.org, dm-devel@redhat.com
Subject: [LSF/MM TOPIC] block, dm: restack queue_limits
Date: Mon, 29 Jan 2018 16:08:37 -0500 [thread overview]
Message-ID: <20180129210836.GA5744@redhat.com> (raw)
We currently don't restack the queue_limits if the lowest, or
intermediate, layer of an IO stack changes.
This is particularly unfortunate in the case of FLUSH/FUA which may
change if/when a HW controller's BBU fails; whereby requiring the device
advertise that it has a volatile write cache (WCE=1).
But in the context of DM, really it'd be best if the entire stack of
devices had their limits restacked if any underlying layer's limits
change.
In the past, Martin and I discussed that we should "just do it" but
never did. Not sure we need a lengthy discussion but figured I'd put it
out there.
Maybe I'll find time, between now and April, to try implementing it.
Thanks,
Mike
next reply other threads:[~2018-01-29 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 21:08 Mike Snitzer [this message]
2018-01-30 15:07 ` [dm-devel] [LSF/MM TOPIC] block, dm: restack queue_limits Hannes Reinecke
2018-01-30 18:49 ` Ewan D. Milne
2018-02-02 5:59 ` NeilBrown
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=20180129210836.GA5744@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-block@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).