Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH nvme-cli v2] nvme: Introduce new 'list-subsys' command
Date: Wed, 13 Dec 2017 08:35:10 -0700	[thread overview]
Message-ID: <20171213153510.GL11218@localhost.localdomain> (raw)
In-Reply-To: <20171213143417.19489-1-jthumshirn@suse.de>

On Wed, Dec 13, 2017@03:34:17PM +0100, Johannes Thumshirn wrote:
> Introduce a 'nvme list-subsys' command to give basic information about
> connected NVMe subsystems.
> 
> Here's an example output of a host connected to two subsystems on the
> target with two paths to each subsystem:
> root at host# nvme list-subsys
> nvme-subsys0 - NQN=nvmf-test
> \
>  +- nvme0 rdma traddr=1.1.1.3 trsvcid=4420 host_traddr=1.1.1.1
>  +- nvme1 rdma traddr=1.1.1.3 trsvcid=4420 host_traddr=1.1.1.2
> nvme-subsys1 - NQN=nvmf-test2
> \
>  +- nvme2 rdma traddr=1.1.1.3 trsvcid=4420 host_traddr=1.1.1.2
>  +- nvme3 rdma traddr=1.1.1.3 trsvcid=4420 host_traddr=1.1.1.1
> 
> Signed-off-by: Johannes Thumshirn <jthumshirn at suse.de>

Thanks, this looks good to me! Applied.

      reply	other threads:[~2017-12-13 15:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 14:34 [PATCH nvme-cli v2] nvme: Introduce new 'list-subsys' command Johannes Thumshirn
2017-12-13 15:35 ` Keith Busch [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=20171213153510.GL11218@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox