From: Sagi Grimberg <sagi@grimberg.me>
To: Daniel Wagner <dwagner@suse.de>, linux-nvme@lists.infradead.org
Subject: Re: [RFC v1 0/3] Unifying fabrics drivers
Date: Tue, 7 Mar 2023 11:26:12 +0200 [thread overview]
Message-ID: <a73ea22a-9871-d152-080e-49c0904dbe94@grimberg.me> (raw)
In-Reply-To: <20230301082737.10021-1-dwagner@suse.de>
> The two fabrics rdma and tcp share a lot of common code. This here is my attempt
> to consolidate the common code.
>
> I've picked just one function (setup admin queue) for this RFC to get a feeling
> and feedback if this is a valid approach or if people hate it. I've left out fc
> for the time being because it differs too much two the other two drivers.
>
> I've tested quickly tcp, rdma is only compile tested.
I think we should make all transports to unify setup/teardown sequences
(i.e. including pcie and fc). Otherwise we are not gaining much.
It will help if we make the ops higher level like
ops.setup_transport(ctrl)
ops.alloc_admin_queue(ctrl)
ops.start_admin_queue(ctrl)
ops.stop_admin_queue(ctrl)
ops.free_admin_queue(ctrl)
ops.alloc_io_queues(ctrl)
ops.start_io_queues(ctrl)
ops.stop_io_queues(ctrl)
ops.free_io_queues(ctrl)
The init/deinit can be folded to alloc/free I think.
This is indeed a much larger effort, but I don't know what
this unification of rdma/tcp buys us really...
next prev parent reply other threads:[~2023-03-07 9:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 8:27 [RFC v1 0/3] Unifying fabrics drivers Daniel Wagner
2023-03-01 8:27 ` [RFC v1 1/3] nvme-rdma: stream line queue functions arguments Daniel Wagner
2023-03-01 8:27 ` [RFC v1 2/3] nvme-rdma: factor rdma specific queue init code out Daniel Wagner
2023-03-01 8:27 ` [RFC v1 3/3] nvme-fabrics: move configure admin queue code to fabrics.c Daniel Wagner
2023-03-02 3:02 ` [RFC v1 0/3] Unifying fabrics drivers Chaitanya Kulkarni
2023-03-02 8:15 ` Daniel Wagner
2023-03-03 23:13 ` James Smart
2023-03-07 12:41 ` Daniel Wagner
2023-03-07 23:55 ` Chaitanya Kulkarni
2023-03-08 8:33 ` Daniel Wagner
2023-03-07 9:26 ` Sagi Grimberg [this message]
2023-03-07 12:28 ` Daniel Wagner
2023-03-07 12:34 ` Sagi Grimberg
2023-03-07 22:09 ` James Smart
2023-03-07 22:09 ` James Smart
2023-03-08 11:38 ` Sagi Grimberg
2023-03-08 15:13 ` James Smart
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=a73ea22a-9871-d152-080e-49c0904dbe94@grimberg.me \
--to=sagi@grimberg.me \
--cc=dwagner@suse.de \
--cc=linux-nvme@lists.infradead.org \
/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).