From: Leon Romanovsky <leon@kernel.org>
To: Magnus Karlsson <magnus.karlsson@gmail.com>
Cc: "Nuno Gonçalves" <nunog@fr24.com>,
"Björn Töpel" <bjorn@kernel.org>,
"Magnus Karlsson" <magnus.karlsson@intel.com>,
"Maciej Fijalkowski" <maciej.fijalkowski@intel.com>,
"Jonathan Lemon" <jonathan.lemon@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Christian Brauner" <brauner@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] xsk: allow remap of fill and/or completion rings
Date: Mon, 20 Mar 2023 15:40:58 +0200 [thread overview]
Message-ID: <20230320134058.GM36557@unreal> (raw)
In-Reply-To: <CAJ8uoz1kbFsttvWNTUdtYcwEa=hQvky2z0Jfn0=9b5v6m_FVXg@mail.gmail.com>
On Mon, Mar 20, 2023 at 01:27:18PM +0100, Magnus Karlsson wrote:
> On Mon, 20 Mar 2023 at 12:09, Leon Romanovsky <leon@kernel.org> wrote:
> >
> > On Mon, Mar 20, 2023 at 10:53:23AM +0000, Nuno Gonçalves wrote:
> > > The remap of fill and completion rings was frowned upon as they
> > > control the usage of UMEM which does not support concurrent use.
> > > At the same time this would disallow the remap of this rings
> > > into another process.
> > >
> > > A possible use case is that the user wants to transfer the socket/
> > > UMEM ownerwhip to another process (via SYS_pidfd_getfd) and so
>
> nit: ownership
>
> > > would need to also remap this rings.
> > >
> > > This will have no impact on current usages and just relaxes the
> > > remap limitation.
> > >
> > > Signed-off-by: Nuno Gonçalves <nunog@fr24.com>
> > > ---
> > > net/xdp/xsk.c | 9 ++++++---
> > > 1 file changed, 6 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/net/xdp/xsk.c b/net/xdp/xsk.c
> > > index 2ac58b282b5eb..2af4ff64b22bd 100644
> > > --- a/net/xdp/xsk.c
> > > +++ b/net/xdp/xsk.c
> > > @@ -1300,10 +1300,11 @@ static int xsk_mmap(struct file *file, struct socket *sock,
> > > {
> > > loff_t offset = (loff_t)vma->vm_pgoff << PAGE_SHIFT;
> > > unsigned long size = vma->vm_end - vma->vm_start;
> > > + int state = READ_ONCE(xs->state);
>
> Reverse Christmas Tree notation here please. Move it one line down to
> after the *xs declaration.
>
> > > struct xdp_sock *xs = xdp_sk(sock->sk);
> > > struct xsk_queue *q = NULL;
> > >
> > > - if (READ_ONCE(xs->state) != XSK_READY)
> > > + if (!(state == XSK_READY || state == XSK_BOUND))
> >
> > This if(..) is actually:
> > if (state != XSK_READY && state != XSK_BOUND)
>
> Nuno had it like that to start with when he sent the patch privately
> to me, but I responded that I prefered the current one. It is easier
> to understand if read out aloud IMO.
"Not equal" is much easier to understand than "not" of whole expression.
> Do not have any strong feelings either way since the statements are equivalent.
>
> > Thanks
next prev parent reply other threads:[~2023-03-20 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 10:53 [PATCH bpf-next] xsk: allow remap of fill and/or completion rings Nuno Gonçalves
2023-03-20 11:03 ` Leon Romanovsky
2023-03-20 12:27 ` Magnus Karlsson
2023-03-20 13:40 ` Leon Romanovsky [this message]
2023-03-20 13:45 ` Magnus Karlsson
2023-03-20 15:04 ` Magnus Karlsson
2023-03-20 20:24 ` kernel test robot
2023-03-20 20:34 ` kernel test robot
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=20230320134058.GM36557@unreal \
--to=leon@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nunog@fr24.com \
--cc=pabeni@redhat.com \
/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).