netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: linux-nfs@vger.kernel.org, lorenzo.bianconi@redhat.com,
	neilb@suse.de,  netdev@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH v5 3/3] NFSD: convert write_ports to netlink command
Date: Thu, 30 Nov 2023 11:22:47 -0500	[thread overview]
Message-ID: <c87becd9af15ad9447030c17dee9c481a8d25442.camel@kernel.org> (raw)
In-Reply-To: <ZWhcc8384pf11sAu@lore-desk>

On Thu, 2023-11-30 at 10:57 +0100, Lorenzo Bianconi wrote:
> > > 
> > > +/* ============== NFSD_CMD_LISTENER_START ============== */
> > > +/* NFSD_CMD_LISTENER_START - do */
> > > +struct nfsd_listener_start_req {
> > > +	struct {
> > > +		__u32 transport_name_len;
> > > +		__u32 port:1;
> > > +	} _present;
> > > +
> > > +	char *transport_name;
> > > +	__u32 port;
> > > +};
> > 
> > How do you deconfigure a listener with this interface? i.e. suppose I
> > want to stop nfsd from listening on a particular port? I think this too
> > is a place where a declarative interface would be better:
> 
> Is it possible with current APIs? as for 2/3 so far I have just added netlink
> counter for current implementation but I am fine to change the logic here to
> better APIs.
> 
> > 

No, I don't think you can do this with the current API at all. I
consider it a major deficiency. I don't think we want to repeat that
mistake in the new interface.

> > Have userland send down a list of the ports that we should currently be
> > listening on, and let the kernel do the work to match the request. Again
> > too, an empty list could mean "close everything".
> > 
> > 

-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2023-11-30 16:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 17:12 [PATCH v5 0/3] convert write_threads, write_version and write_ports to netlink commands Lorenzo Bianconi
2023-11-29 17:12 ` [PATCH v5 1/3] NFSD: convert write_threads to netlink command Lorenzo Bianconi
2023-11-29 18:13   ` Jeff Layton
2023-11-29 18:31     ` Chuck Lever
2023-11-30  0:32       ` Jakub Kicinski
2023-11-29 17:12 ` [PATCH v5 2/3] NFSD: convert write_version " Lorenzo Bianconi
2023-11-29 18:23   ` Jeff Layton
2023-11-30  9:45     ` Lorenzo Bianconi
2023-11-30 16:17       ` Jeff Layton
2023-11-30 16:11     ` Chuck Lever
2023-11-30 16:25       ` Lorenzo Bianconi
2023-11-30 16:29         ` Chuck Lever
2023-11-30 16:32           ` Lorenzo Bianconi
2023-11-30  0:28   ` Jakub Kicinski
2023-11-30 10:32     ` Lorenzo Bianconi
2023-12-01  7:28       ` Jakub Kicinski
2023-12-05 20:33   ` Simon Horman
2023-11-29 17:12 ` [PATCH v5 3/3] NFSD: convert write_ports " Lorenzo Bianconi
2023-11-29 18:28   ` Jeff Layton
2023-11-30  9:57     ` Lorenzo Bianconi
2023-11-30 16:22       ` Jeff Layton [this message]
2023-11-30 16:55         ` Jeff Layton
2023-11-30 17:39           ` Chuck Lever
2023-11-30 18:01             ` Jeff Layton
2023-11-30 18:34               ` Chuck Lever
2023-12-05 20:37   ` Simon Horman

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=c87becd9af15ad9447030c17dee9c481a8d25442.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=lorenzo@kernel.org \
    --cc=neilb@suse.de \
    --cc=netdev@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).