From: Logan Gunthorpe <logang@deltatee.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Max Gurtovoy <maxg@mellanox.com>,
Stephen Bates <sbates@raithlin.com>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v6 02/16] chardev: introduce cdev_get_by_path()
Date: Thu, 25 Jul 2019 12:16:08 -0600 [thread overview]
Message-ID: <824d6fd3-56ff-7b69-9e0a-52198a2f4184@deltatee.com> (raw)
In-Reply-To: <20190725181041.GB32305@kroah.com>
On 2019-07-25 12:10 p.m., Greg Kroah-Hartman wrote:
> On Thu, Jul 25, 2019 at 11:53:20AM -0600, Logan Gunthorpe wrote:
>>
>>
>> On 2019-07-25 11:40 a.m., Greg Kroah-Hartman wrote:
>>> On Thu, Jul 25, 2019 at 11:23:21AM -0600, Logan Gunthorpe wrote:
>>>> cdev_get_by_path() attempts to retrieve a struct cdev from
>>>> a path name. It is analagous to blkdev_get_by_path().
>>>>
>>>> This will be necessary to create a nvme_ctrl_get_by_path()to
>>>> support NVMe-OF passthru.
>>>
>>> Ick, why? Why would a cdev have a "pathname"?
>>
>> So we can go from "/dev/nvme0" (which points to a char device) to its
>> struct cdev and eventually it's struct nvme_ctrl. Doing it this way also
>> allows supporting symlinks that might be created by udev rules.
>>
>> This is very similar to blkdev_get_by_path() that lets regular NVMe-OF
>> obtain the struct block_device from a path.
>>
>> I didn't think this would be all that controversial.
>>
>>> What is "NVMe-OF passthru"? Why does a char device node have anything
>>> to do with NVMe?
>>
>> NVME-OF passthru is support for NVME over fabrics to directly target a
>> regular NVMe controller and thus export an entire NVMe device to a
>> remote system. We need to be able to tell the kernel which controller to
>> use and IMO a path to the device file is the best way as it allows us to
>> support symlinks created by udev.
>
> open() in userspace handles symlinks just fine, what crazy interface
> passes a string to try to find a char device node that is not open()?
configfs. Which I'm stuck with seeing nvme-of already uses that for
configuration and I don't think that's going to change...
> And why do you need a char device at all anyway? Is this just the
> "normal" nvme controller's character device node?
Yes.
Logan
next prev parent reply other threads:[~2019-07-25 18:16 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 17:23 [PATCH v6 00/16] nvmet: add target passthru commands support Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 01/16] chardev: factor out cdev_lookup() helper Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 02/16] chardev: introduce cdev_get_by_path() Logan Gunthorpe
2019-07-25 17:40 ` Greg Kroah-Hartman
2019-07-25 17:53 ` Logan Gunthorpe
2019-07-25 17:58 ` Matthew Wilcox
2019-07-25 18:08 ` Logan Gunthorpe
2019-07-25 18:08 ` Greg Kroah-Hartman
2019-07-25 18:14 ` Logan Gunthorpe
2019-07-25 18:27 ` Greg Kroah-Hartman
2019-07-25 18:36 ` Logan Gunthorpe
2019-07-25 19:02 ` Sagi Grimberg
2019-07-25 19:34 ` Greg Kroah-Hartman
2019-07-25 19:37 ` Sagi Grimberg
2019-07-25 19:43 ` Greg Kroah-Hartman
2019-07-25 19:45 ` Sagi Grimberg
2019-07-25 19:43 ` Sagi Grimberg
2019-07-25 19:41 ` Logan Gunthorpe
2019-07-25 19:00 ` Matthew Wilcox
2019-07-25 19:05 ` Sagi Grimberg
2019-07-25 19:11 ` Matthew Wilcox
2019-07-25 19:24 ` Logan Gunthorpe
2019-07-25 19:26 ` Matthew Wilcox
2019-07-25 19:31 ` Logan Gunthorpe
2019-07-25 23:55 ` Al Viro
2019-07-26 4:29 ` Sagi Grimberg
2019-07-26 7:13 ` Greg Kroah-Hartman
2019-07-26 15:46 ` Logan Gunthorpe
2019-07-25 19:31 ` Sagi Grimberg
2019-07-25 18:10 ` Greg Kroah-Hartman
2019-07-25 18:16 ` Logan Gunthorpe [this message]
2019-07-25 17:23 ` [PATCH v6 03/16] chardev: export cdev_put() Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 04/16] nvme-core: introduce nvme_get_by_path() Logan Gunthorpe
2019-07-25 17:50 ` Matthew Wilcox
2019-07-25 17:54 ` Logan Gunthorpe
2019-07-25 19:58 ` Keith Busch
2019-07-25 20:12 ` Sagi Grimberg
2019-07-25 20:28 ` Logan Gunthorpe
2019-07-25 20:31 ` Keith Busch
2019-07-25 20:37 ` Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 05/16] nvme-core: export existing ctrl and ns interfaces Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 06/16] nvmet: add return value to nvmet_add_async_event() Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 07/16] nvmet: make nvmet_copy_ns_identifier() non-static Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 08/16] nvmet-passthru: update KConfig with config passthru option Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 09/16] nvmet-passthru: add passthru code to process commands Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 10/16] nvmet-passthru: add enable/disable helpers Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 11/16] nvmet-core: allow one host per passthru-ctrl Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 12/16] nvmet-core: don't check the data len for pt-ctrl Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 13/16] nvmet-configfs: introduce passthru configfs interface Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 14/16] block: don't check blk_rq_is_passthrough() in blk_do_io_stat() Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 15/16] block: call blk_account_io_start() in blk_execute_rq_nowait() Logan Gunthorpe
2019-07-25 17:23 ` [PATCH v6 16/16] nvmet-passthru: support block accounting Logan Gunthorpe
2019-07-26 6:23 ` [PATCH v6 00/16] nvmet: add target passthru commands support Hannes Reinecke
2019-07-26 17:07 ` Logan Gunthorpe
2019-07-26 22:21 ` Sagi Grimberg
2019-07-26 22:37 ` Logan Gunthorpe
2019-07-26 23:13 ` Sagi Grimberg
2019-07-27 0:09 ` Logan Gunthorpe
2019-07-27 0:50 ` Stephen Bates
2019-07-29 16:15 ` Sagi Grimberg
2019-07-29 16:17 ` Logan Gunthorpe
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=824d6fd3-56ff-7b69-9e0a-52198a2f4184@deltatee.com \
--to=logang@deltatee.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=axboe@fb.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=maxg@mellanox.com \
--cc=sagi@grimberg.me \
--cc=sbates@raithlin.com \
--cc=viro@zeniv.linux.org.uk \
/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).