From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 2/2] nvmet: don't split large I/Os unconditionally
Date: Fri, 28 Sep 2018 17:19:00 +0200 [thread overview]
Message-ID: <20180928151900.GA8279@lst.de> (raw)
In-Reply-To: <20180928004407.25237-1-sagi@grimberg.me>
On Thu, Sep 27, 2018@05:44:07PM -0700, Sagi Grimberg wrote:
> If we know that the I/O size exceeds our inline bio vec, no
> point using it and split the rest to begin with.
In theory there would be a point if the I/O size did exactly fit
the inline bio + a maximum size allocated bio. Probably not worth
optimizing for, but maybe worth an updated changelog.
prev parent reply other threads:[~2018-09-28 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 0:44 [PATCH 2/2] nvmet: don't split large I/Os unconditionally Sagi Grimberg
2018-09-28 15:19 ` Christoph Hellwig [this message]
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=20180928151900.GA8279@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.