All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH nvme-cli] fabrics: add option to override drivers queue depth
Date: Wed, 10 May 2017 14:38:34 -0400	[thread overview]
Message-ID: <20170510183834.GH2572@localhost.localdomain> (raw)
In-Reply-To: <20170510144120.GA24518@lst.de>

On Wed, May 10, 2017@04:41:21PM +0200, Christoph Hellwig wrote:
> On Wed, May 10, 2017@11:04:12AM +0200, Johannes Thumshirn wrote:
> > Currently it is not possible to override the fabrics drivers default queue
> > depth with the nvme userspace utility, but only when manually writing the
> > parameters to the /dev/nvme-fabrics character device.
> > 
> > Add an option to override the drivers default queue depth for NVMe over
> > fabrics.
> 
> Looks fine, but we should probably also add this to connect-all.

Agreed. I applied the one as-is, and will apply the connect-all update
when that's posted.

  reply	other threads:[~2017-05-10 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10  9:04 [PATCH nvme-cli] fabrics: add option to override drivers queue depth Johannes Thumshirn
2017-05-10 14:41 ` Christoph Hellwig
2017-05-10 18:38   ` Keith Busch [this message]
2017-05-11  7:28     ` Johannes Thumshirn

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=20170510183834.GH2572@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.