From: Jason Gunthorpe <jgg@nvidia.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Chuck Lever III <chuck.lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: Safe to delete rpcrdma.ko loading start-up code
Date: Tue, 21 May 2024 12:23:25 -0300 [thread overview]
Message-ID: <20240521152325.GG20229@nvidia.com> (raw)
In-Reply-To: <46c36727-ef93-44ca-9741-df2325d4420c@grimberg.me>
On Tue, May 21, 2024 at 05:12:23PM +0300, Sagi Grimberg wrote:
> > > > > I also see that srp(t) and iser(t) are loaded too.. IIRC these are
> > > > > loaded by their userspace counterparts as well (or at least they
> > > > > should).
> > > > And AFIAK, these don't have a way to autoload at all. autoload
> > > > requires the kernel to call request_module..
> > > nvme/nvmet/isert are requested by the kernel.
> > How? What is the interface to trigger request_module?
>
> On the host, writing to the nvme-fabrics misc device a comma-separated
> connection string
> contains a transport string, which triggers the corresponding module to be
> requested.
But how did nvme-fabrics even get loaded to write to it's config fs in
the first place?
Jason
next prev parent reply other threads:[~2024-05-21 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 18:05 Safe to delete rpcrdma.ko loading start-up code Chuck Lever III
2024-05-21 9:04 ` Sagi Grimberg
2024-05-21 12:43 ` Jason Gunthorpe
2024-05-21 13:05 ` Sagi Grimberg
2024-05-21 13:37 ` Jason Gunthorpe
2024-05-21 14:12 ` Sagi Grimberg
2024-05-21 15:23 ` Jason Gunthorpe [this message]
2024-05-21 16:10 ` Sagi Grimberg
2024-05-21 16:37 ` Jason Gunthorpe
2024-05-21 20:30 ` Sagi Grimberg
2024-05-21 23:29 ` Jason Gunthorpe
2024-05-22 10:50 ` Sagi Grimberg
2024-05-22 7:57 ` Zhu Yanjun
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=20240521152325.GG20229@nvidia.com \
--to=jgg@nvidia.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sagi@grimberg.me \
/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.