From: Jason Gunthorpe <jgg@ziepe.ca>
To: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
Cc: Chuck Lever <chucklever@gmail.com>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org
Subject: Re: RDMA subsystem namespace related questions (was Re: Finding the namespace of a struct ib_device)
Date: Fri, 16 Oct 2020 15:54:43 -0300 [thread overview]
Message-ID: <20201016185443.GA37159@ziepe.ca> (raw)
In-Reply-To: <4e630f85-c684-1e56-bb68-22c37872c728@oracle.com>
On Mon, Oct 12, 2020 at 04:20:40PM +0800, Ka-Cheong Poon wrote:
> On 10/9/20 11:34 PM, Jason Gunthorpe wrote:
>
> > Yes, because namespaces are fundamentally supposed to be anchored in
> > the processes inside the namespace.
> >
> > Having the kernel jump in and start opening holes as soon as a
> > namespace is created is just wrong.
> >
> > At a bare minimum the listener should not exist until something in the
> > namespace is willing to work with RDS.
>
>
> As I mentioned in a previous email, starting is not the problem. It
> is the problem of deleting a namespace.
Starting and ending are symmetric. When the last thing inside the
namespace stops needing RDS then RDS should close down the cm_id's.
Jason
next prev parent reply other threads:[~2020-10-16 18:54 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 14:02 Finding the namespace of a struct ib_device Ka-Cheong Poon
2020-09-03 17:39 ` Jason Gunthorpe
2020-09-04 4:01 ` Ka-Cheong Poon
2020-09-04 11:32 ` Jason Gunthorpe
2020-09-04 14:02 ` Ka-Cheong Poon
2020-09-06 7:44 ` Leon Romanovsky
2020-09-07 3:33 ` Ka-Cheong Poon
2020-09-07 7:18 ` Leon Romanovsky
2020-09-07 8:24 ` Ka-Cheong Poon
2020-09-07 9:04 ` Leon Romanovsky
2020-09-07 9:28 ` Ka-Cheong Poon
2020-09-07 10:22 ` Leon Romanovsky
2020-09-07 13:48 ` Ka-Cheong Poon
2020-09-29 16:57 ` RDMA subsystem namespace related questions (was Re: Finding the namespace of a struct ib_device) Ka-Cheong Poon
2020-09-29 17:40 ` Jason Gunthorpe
2020-09-30 10:32 ` Ka-Cheong Poon
2020-10-02 14:04 ` Jason Gunthorpe
2020-10-05 10:27 ` Ka-Cheong Poon
2020-10-05 13:16 ` Jason Gunthorpe
2020-10-05 13:57 ` Ka-Cheong Poon
2020-10-05 14:25 ` Jason Gunthorpe
2020-10-05 15:02 ` Ka-Cheong Poon
2020-10-05 15:45 ` Jason Gunthorpe
2020-10-06 9:36 ` Ka-Cheong Poon
2020-10-06 12:46 ` Jason Gunthorpe
2020-10-07 8:38 ` Ka-Cheong Poon
2020-10-07 11:16 ` Leon Romanovsky
2020-10-08 10:22 ` Ka-Cheong Poon
2020-10-08 10:36 ` Leon Romanovsky
2020-10-08 11:08 ` Ka-Cheong Poon
2020-10-08 16:08 ` Jason Gunthorpe
2020-10-08 16:21 ` Chuck Lever
2020-10-08 16:46 ` Jason Gunthorpe
2020-10-09 4:49 ` Ka-Cheong Poon
2020-10-09 14:39 ` Jason Gunthorpe
2020-10-09 14:48 ` Chuck Lever
2020-10-09 14:57 ` Jason Gunthorpe
2020-10-09 15:00 ` Chuck Lever
2020-10-09 15:07 ` Jason Gunthorpe
2020-10-09 15:27 ` Chuck Lever
2020-10-09 15:34 ` Jason Gunthorpe
2020-10-09 15:52 ` Chuck Lever
2020-10-12 8:20 ` Ka-Cheong Poon
2020-10-16 18:54 ` Jason Gunthorpe [this message]
2020-10-16 20:49 ` Chuck Lever
2020-10-19 18:31 ` Jason Gunthorpe
2020-10-07 12:28 ` Jason Gunthorpe
2020-10-08 10:49 ` Ka-Cheong Poon
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=20201016185443.GA37159@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=chucklever@gmail.com \
--cc=ka-cheong.poon@oracle.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.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).