All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH v2 2/2] nvme: use a single NVME_AQ_DEPTH and relax it to 32
Date: Mon, 19 Jun 2017 12:01:03 -0400	[thread overview]
Message-ID: <20170619160103.GA21765@localhost.localdomain> (raw)
In-Reply-To: <1497791759-5754-2-git-send-email-sagi@grimberg.me>

On Sun, Jun 18, 2017@04:15:59PM +0300, Sagi Grimberg wrote:
> No need to differentiate fabrics from pci/loop, also lower
> it to 32 as we don't really need 256 inflight admin commands.

Might want to check with Jens on reducing the count. d31af0a325ca4f increased the
limit from 64 to 256 for a particular use case.

  parent reply	other threads:[~2017-06-19 16:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-18 13:15 [PATCH v2 1/2] nvme-core: change commas to semicolons in nvme_get_log_page Sagi Grimberg
2017-06-18 13:15 ` [PATCH v2 2/2] nvme: use a single NVME_AQ_DEPTH and relax it to 32 Sagi Grimberg
2017-06-18 15:10   ` Max Gurtovoy
2017-06-19  6:58   ` Christoph Hellwig
2017-06-19 16:01   ` Keith Busch [this message]
2017-06-19 16:47     ` Sagi Grimberg
2017-06-19 16:28   ` Martin K. Petersen
2017-06-18 15:10 ` [PATCH v2 1/2] nvme-core: change commas to semicolons in nvme_get_log_page Max Gurtovoy
2017-06-19  6:59 ` Christoph Hellwig
2017-06-19  8:06   ` Sagi Grimberg

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=20170619160103.GA21765@localhost.localdomain \
    --to=keith.busch@intel.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 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.