From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: make sure ns head inherits underlying device limits
Date: Mon, 22 Oct 2018 10:57:52 +0200 [thread overview]
Message-ID: <20181022085752.GD18755@lst.de> (raw)
In-Reply-To: <20181019222450.25397-1-sagi@grimberg.me>
On Fri, Oct 19, 2018@03:24:50PM -0700, Sagi Grimberg wrote:
> Whenever we update ns_head info, we need to make sure it is still
> compatible with all underlying backing devices. Start with unlimited
> stacking limits, and every info update iterate over siblings and
> adjust queue limits.
Why? Neither the block layer, nor the nvme multipath code should
even look at this values.
next prev parent reply other threads:[~2018-10-22 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 22:24 [PATCH] nvme: make sure ns head inherits underlying device limits Sagi Grimberg
2018-10-22 8:57 ` Christoph Hellwig [this message]
2018-10-23 0:22 ` Sagi Grimberg
2018-10-26 7:53 ` Christoph Hellwig
2018-10-30 18:11 ` Sagi Grimberg
2018-10-31 5:27 ` 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=20181022085752.GD18755@lst.de \
--to=hch@lst.de \
/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.