From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: make sure ns head inherits underlying device limits
Date: Fri, 26 Oct 2018 09:53:19 +0200 [thread overview]
Message-ID: <20181026075319.GC5092@lst.de> (raw)
In-Reply-To: <70bcef36-48da-cae7-4e23-ac9b01814a74@grimberg.me>
On Mon, Oct 22, 2018@05:22:15PM -0700, Sagi Grimberg wrote:
> Without this patch at least max_segments and max_hw_sectors of the head
> device node are degenerated to defaults that have nothing to do with the
> underlying device limits.
>
> This can result in unnecessary bio splitting for the head device
> node...
But we never split bios for the multipath queue!
next prev parent reply other threads:[~2018-10-26 7:53 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
2018-10-23 0:22 ` Sagi Grimberg
2018-10-26 7:53 ` Christoph Hellwig [this message]
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=20181026075319.GC5092@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.