Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@fb.com (Jens Axboe)
Subject: [PATCH] NVMe: Set queue max segments
Date: Mon, 17 Aug 2015 15:51:55 -0600	[thread overview]
Message-ID: <55D2577B.9020905@fb.com> (raw)
In-Reply-To: <1439417874-8925-1-git-send-email-keith.busch@intel.com>

On 08/12/2015 04:17 PM, Keith Busch wrote:
> This sets the queue's max segment size to match the device's
> capabilities. The default of 128 is usable until a device's transfer
> capability exceeds 512k, assuming a device page size of 4k. Many nvme
> devices exceed that transfer limit, so this lets the block layer know what
> kind of commands it to allow to form rather than unnecessarily split them.
>
> One additional segment is added to account for a transfer that may start
> in the middle of a page.

Applied for 4.3.

-- 
Jens Axboe

      parent reply	other threads:[~2015-08-17 21:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 22:17 [PATCH] NVMe: Set queue max segments Keith Busch
2015-08-13  6:38 ` Christoph Hellwig
2015-08-13 13:52   ` Keith Busch
2015-08-17 19:12     ` Christoph Hellwig
2015-08-17 21:51 ` 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=55D2577B.9020905@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