linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: axboe@fb.com (Jens Axboe)
Subject: [PATCH] block: split bios to max possible length
Date: Tue, 12 Jan 2016 15:11:30 -0700	[thread overview]
Message-ID: <56957A12.8040902@fb.com> (raw)
In-Reply-To: <1452636519-32697-1-git-send-email-keith.busch@intel.com>

On 01/12/2016 03:08 PM, Keith Busch wrote:
> This splits bio in the middle of a vector to form the largest possible
> bio at the h/w's desired alignment, and guarantees the bio being split
> will have some data.
>
> The criteria for splitting is changed from the max sectors to the h/w's
> optimal sector alignment if it is provided. For h/w that advertise their
> block storage's underlying chunk size, it's a big performance win to not
> submit commands that cross them. If sector alignment is not provided,
> this patch uses the max sectors as before.
>
> This addresses the performance issue commit d380561113 attempted to
> fix, but was reverted due to splitting logic error.

Thanks Keith, added for 4.5.

-- 
Jens Axboe

      reply	other threads:[~2016-01-12 22:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 22:08 [PATCH] block: split bios to max possible length Keith Busch
2016-01-12 22:11 ` Jens Axboe [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=56957A12.8040902@fb.com \
    --to=axboe@fb.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 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).