All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: dccp@vger.kernel.org
Subject: Re: [PATCH RFC] io_uring: Pass whole sqe to commands
Date: Tue, 11 Apr 2023 12:22:50 +0000	[thread overview]
Message-ID: <ZDVRGoDZo1tTbmZu@gmail.com> (raw)
In-Reply-To: <20230406165705.3161734-1-leitao@debian.org>

On Fri, Apr 07, 2023 at 12:51:44PM -0600, Keith Busch wrote:
> > @@ -63,14 +63,15 @@ EXPORT_SYMBOL_GPL(io_uring_cmd_done);
> >  int io_uring_cmd_prep_async(struct io_kiocb *req)
> >  {
> >  	struct io_uring_cmd *ioucmd = io_kiocb_to_cmd(req, struct io_uring_cmd);
> > -	size_t cmd_size;
> > +	size_t size = sizeof(struct io_uring_sqe);
> >  
> >  	BUILD_BUG_ON(uring_cmd_pdu_size(0) != 16);
> >  	BUILD_BUG_ON(uring_cmd_pdu_size(1) != 80);
> 
> One minor suggestion. The above is the only user of uring_cmd_pdu_size() now,
> which is kind of a convoluted way to enfoce the offset of the 'cmd' field. It
> may be more clear to replace these with:

I agree with you here. Basically it is a bug if the payload (pdu) size is
is different than 16 for single SQE or != 80 for extended SQE.

So, basically it is checking for two things:
   * the cmd offset is 48
   * the io_uring_sqe struct is 64

Since this is a uapi, I am not confidence that they will change at all.
I can replace the code with your suggestion.

> 	BUILD_BUG_ON(offsetof(struct io_uring_sqe, cmd) = 48);

It should be "offset(struct io_uring_sqe, cmd) != 48)", right?

Thanks for the review!

WARNING: multiple messages have this Message-ID (diff)
From: Breno Leitao <leitao@debian.org>
To: Keith Busch <kbusch@kernel.org>
Cc: asml.silence@gmail.com, axboe@kernel.dk, davem@davemloft.net,
	dccp@vger.kernel.org, dsahern@kernel.org, edumazet@google.com,
	io-uring@vger.kernel.org, kuba@kernel.org, leit@fb.com,
	linux-kernel@vger.kernel.org, marcelo.leitner@gmail.com,
	matthieu.baerts@tessares.net, mptcp@lists.linux.dev,
	netdev@vger.kernel.org, pabeni@redhat.com,
	willemdebruijn.kernel@gmail.com
Subject: Re: [PATCH RFC] io_uring: Pass whole sqe to commands
Date: Tue, 11 Apr 2023 05:22:50 -0700	[thread overview]
Message-ID: <ZDVRGoDZo1tTbmZu@gmail.com> (raw)
In-Reply-To: <ZDBmQOhbyU0iLhMw@kbusch-mbp.dhcp.thefacebook.com>

On Fri, Apr 07, 2023 at 12:51:44PM -0600, Keith Busch wrote:
> > @@ -63,14 +63,15 @@ EXPORT_SYMBOL_GPL(io_uring_cmd_done);
> >  int io_uring_cmd_prep_async(struct io_kiocb *req)
> >  {
> >  	struct io_uring_cmd *ioucmd = io_kiocb_to_cmd(req, struct io_uring_cmd);
> > -	size_t cmd_size;
> > +	size_t size = sizeof(struct io_uring_sqe);
> >  
> >  	BUILD_BUG_ON(uring_cmd_pdu_size(0) != 16);
> >  	BUILD_BUG_ON(uring_cmd_pdu_size(1) != 80);
> 
> One minor suggestion. The above is the only user of uring_cmd_pdu_size() now,
> which is kind of a convoluted way to enfoce the offset of the 'cmd' field. It
> may be more clear to replace these with:

I agree with you here. Basically it is a bug if the payload (pdu) size is
is different than 16 for single SQE or != 80 for extended SQE.

So, basically it is checking for two things:
   * the cmd offset is 48
   * the io_uring_sqe struct is 64

Since this is a uapi, I am not confidence that they will change at all.
I can replace the code with your suggestion.

> 	BUILD_BUG_ON(offsetof(struct io_uring_sqe, cmd) == 48);

It should be "offset(struct io_uring_sqe, cmd) != 48)", right?

Thanks for the review!

  parent reply	other threads:[~2023-04-11 12:22 UTC|newest]

Thread overview: 108+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 16:57 [PATCH RFC] io_uring: Pass whole sqe to commands Breno Leitao
2023-04-06 16:57 ` Breno Leitao
2023-04-06 17:50 ` io_uring: Pass whole sqe to commands: Tests Results MPTCP CI
2023-04-07 18:51 ` [PATCH RFC] io_uring: Pass whole sqe to commands Keith Busch
2023-04-07 18:51   ` Keith Busch
2023-04-07 19:43 ` io_uring: Pass whole sqe to commands: Tests Results MPTCP CI
2023-04-11 12:22 ` Breno Leitao [this message]
2023-04-11 12:22   ` [PATCH RFC] io_uring: Pass whole sqe to commands Breno Leitao
2023-04-11 12:39 ` Pavel Begunkov
2023-04-11 12:39   ` Pavel Begunkov
2023-04-13  2:56 ` Ming Lei
2023-04-13  2:56   ` Ming Lei
2023-04-13 16:47 ` Breno Leitao
2023-04-13 16:47   ` Breno Leitao
2023-04-14  2:12 ` Ming Lei
2023-04-14  2:12   ` Ming Lei
2023-04-14 13:12 ` Pavel Begunkov
2023-04-14 13:12   ` Pavel Begunkov
2023-04-14 13:59 ` Ming Lei
2023-04-14 13:59   ` Ming Lei
2023-04-14 14:56 ` Pavel Begunkov
2023-04-14 14:56   ` Pavel Begunkov
2023-04-16  9:51 ` Ming Lei
2023-04-16  9:51   ` Ming Lei
  -- strict thread matches above, loose matches on Subject: below --
2023-04-06 14:43 [RFC PATCH 4/4] net: add uring_cmd callback to raw "protocol" Breno Leitao
2023-04-06 14:43 ` Breno Leitao
2023-04-06 14:43 [RFC PATCH 3/4] net: add uring_cmd callback to TCP Breno Leitao
2023-04-06 14:43 ` Breno Leitao
2023-04-06 20:35 ` kernel test robot
2023-04-06 14:43 [RFC PATCH 2/4] net: add uring_cmd callback to UDP Breno Leitao
2023-04-06 14:43 ` Breno Leitao
2023-04-06 19:03 ` kernel test robot
2023-04-11 12:54 ` Pavel Begunkov
2023-04-11 12:54   ` Pavel Begunkov
2023-04-06 14:43 [RFC PATCH 1/4] net: wire up support for file_operations->uring_cmd() Breno Leitao
2023-04-06 14:43 ` Breno Leitao
2023-04-06 14:43 [PATCH 0/5] add initial io_uring_cmd support for sockets Breno Leitao
2023-04-06 14:43 ` Breno Leitao
2023-04-06 15:34 ` Willem de Bruijn
2023-04-06 15:34   ` Willem de Bruijn
2023-04-06 15:59 ` Breno Leitao
2023-04-06 15:59   ` Breno Leitao
2023-04-06 16:41 ` Keith Busch
2023-04-06 16:41   ` Keith Busch
2023-04-06 16:49 ` Jens Axboe
2023-04-06 16:49   ` Jens Axboe
2023-04-06 16:58 ` Breno Leitao
2023-04-06 16:58   ` Breno Leitao
2023-04-06 18:16 ` Willem de Bruijn
2023-04-06 18:16   ` Willem de Bruijn
2023-04-07  2:46 ` David Ahern
2023-04-07  2:46   ` David Ahern
2023-04-11 11:59 ` Breno Leitao
2023-04-11 12:00   ` Breno Leitao
2023-04-11 14:36 ` David Ahern
2023-04-11 14:36   ` David Ahern
2023-04-11 14:41 ` Jens Axboe
2023-04-11 14:41   ` Jens Axboe
2023-04-11 14:51 ` Willem de Bruijn
2023-04-11 14:51   ` Willem de Bruijn
2023-04-11 14:54 ` Jens Axboe
2023-04-11 14:54   ` Jens Axboe
2023-04-11 15:00 ` Willem de Bruijn
2023-04-11 15:00   ` Willem de Bruijn
2023-04-11 15:06 ` Jens Axboe
2023-04-11 15:06   ` Jens Axboe
2023-04-11 15:10 ` David Ahern
2023-04-11 15:10   ` David Ahern
2023-04-11 15:17 ` Jens Axboe
2023-04-11 15:17   ` Jens Axboe
2023-04-11 15:24 ` Willem de Bruijn
2023-04-11 15:24   ` Willem de Bruijn
2023-04-11 15:27 ` David Ahern
2023-04-11 15:27   ` David Ahern
2023-04-11 15:28 ` Jens Axboe
2023-04-11 15:28   ` Jens Axboe
2023-04-11 15:29 ` Jens Axboe
2023-04-11 15:29   ` Jens Axboe
2023-04-12  7:39 ` David Laight
2023-04-12  7:39   ` David Laight
2023-04-12 13:53 ` Breno Leitao
2023-04-12 13:53   ` Breno Leitao
2023-04-12 14:28 ` Willem de Bruijn
2023-04-12 14:28   ` Willem de Bruijn
2023-04-13  0:02 ` Breno Leitao
2023-04-13  0:02   ` Breno Leitao
2023-04-13 14:24 ` Willem de Bruijn
2023-04-13 14:24   ` Willem de Bruijn
2023-04-13 14:45 ` Jakub Kicinski
2023-04-13 14:45   ` Jakub Kicinski
2023-04-13 14:57 ` David Laight
2023-04-13 14:57   ` David Laight
2023-04-18 13:23 ` Breno Leitao
2023-04-18 13:23   ` Breno Leitao
2023-04-18 19:41 ` Willem de Bruijn
2023-04-18 19:41   ` Willem de Bruijn
2023-04-20 14:43 ` Breno Leitao
2023-04-20 14:43   ` Breno Leitao
2023-04-20 16:48 ` Willem de Bruijn
2023-04-20 16:48   ` Willem de Bruijn
2023-05-02  9:21 ` Adrien Delorme
2023-05-02  9:21   ` Adrien Delorme
2023-05-02 13:03 ` Pavel Begunkov
2023-05-02 13:03   ` Pavel Begunkov
2023-05-03 13:11 ` Adrien Delorme
2023-05-03 13:11   ` Adrien Delorme
2023-05-03 13:27 ` David Laight
2023-05-03 13:27   ` David Laight

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=ZDVRGoDZo1tTbmZu@gmail.com \
    --to=leitao@debian.org \
    --cc=dccp@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 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.