From: Johannes Thumshirn <jthumshirn@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, keith.busch@intel.com,
linux-block@vger.kernel.org, Ming Lin <ming.l@ssi.samsung.com>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 4/8] nvme: add fabrics sysfs attributes
Date: Tue, 7 Jun 2016 10:52:17 +0200 [thread overview]
Message-ID: <20160607085217.mp7ppvdmvzwwi36b@c203.arch.suse.de> (raw)
In-Reply-To: <1465248119-17875-5-git-send-email-hch@lst.de>
On Mon, Jun 06, 2016 at 11:21:55PM +0200, Christoph Hellwig wrote:
> - delete_controller: This attribute allows to delete a controller.
> A driver is not obligated to support it (pci doesn't) so it is
> created only if the driver supports it. The new fabrics drivers
> will support it (essentialy a disconnect operation).
>
> Usage:
> echo > /sys/class/nvme/nvme0/delete_controller
>
> - subsysnqn: This attribute shows the subsystem nqn of the configured
> device. If a driver does not implement the get_subsysnqn method, the
> file will not appear in sysfs.
>
> - transport: This attribute shows the transport name. Added a "name"
> field to struct nvme_ctrl_ops.
>
> For loop,
> cat /sys/class/nvme/nvme0/transport
> loop
>
> For RDMA,
> cat /sys/class/nvme/nvme0/transport
> rdma
>
> For PCIe,
> cat /sys/class/nvme/nvme0/transport
> pcie
>
> - address: This attributes shows the controller address. The fabrics
> drivers that will implement get_address can show the address of the
> connected controller.
>
> example:
> cat /sys/class/nvme/nvme0/address
> traddr=192.168.2.2,trsvcid=1023
Can you please add this to Documentation/ABI/ as well?
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2016-06-07 8:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 21:21 generic NVMe over Fabrics library support Christoph Hellwig
2016-06-06 21:21 ` [PATCH 1/8] blk-mq: add blk_mq_alloc_request_hctx Christoph Hellwig
2016-06-07 14:57 ` Keith Busch
2016-06-07 15:27 ` Ming Lin
2016-06-07 23:21 ` Ming Lin
2016-06-08 4:49 ` Jens Axboe
2016-06-08 5:20 ` Ming Lin
2016-06-08 11:56 ` Christoph Hellwig
2016-06-08 11:54 ` Christoph Hellwig
2016-06-06 21:21 ` [PATCH 2/8] nvme: allow transitioning from NEW to LIVE state Christoph Hellwig
2016-06-06 21:21 ` [PATCH 3/8] nvme: Modify and export sync command submission for fabrics Christoph Hellwig
2016-06-06 21:21 ` [PATCH 4/8] nvme: add fabrics sysfs attributes Christoph Hellwig
2016-06-07 8:52 ` Johannes Thumshirn [this message]
2016-06-07 10:51 ` Christoph Hellwig
2016-06-07 15:21 ` Christoph Hellwig
2016-06-06 21:21 ` [PATCH 5/8] nvme.h: add NVMe over Fabrics definitions Christoph Hellwig
2016-06-06 21:21 ` [PATCH 6/8] nvme-fabrics: add a generic NVMe over Fabrics library Christoph Hellwig
2016-06-06 21:21 ` [PATCH 7/8] nvme.h: Add keep-alive opcode and identify controller attribute Christoph Hellwig
2016-06-06 21:21 ` [PATCH 8/8] nvme: add keep-alive support Christoph Hellwig
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=20160607085217.mp7ppvdmvzwwi36b@c203.arch.suse.de \
--to=jthumshirn@suse.de \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.l@ssi.samsung.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).