public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Caleb Sander Mateos <csander@purestorage.com>
To: Keith Busch <kbusch@meta.com>
Cc: axboe@kernel.dk, Keith Busch <kbusch@kernel.org>,
	 io-uring Mailing List <io-uring@vger.kernel.org>
Subject: Re: [PATCHv4 0/1] io_uring: mixed submission queue entries sizes
Date: Fri, 10 Oct 2025 13:44:52 -0700	[thread overview]
Message-ID: <CADUfDZoJkk6a6Kx4=MAnPbQHycA5AXe=MUrPkuWV8fmjb=H3HQ@mail.gmail.com> (raw)
In-Reply-To: <20251009143645.2659663-1-kbusch@meta.com>

FYI looks like you may have the wrong email address for the mailing
list. Should be io-uring@ instead of io_uring@. CCing the correct
address.

Best,
Caleb

On Thu, Oct 9, 2025 at 7:37 AM Keith Busch <kbusch@meta.com> wrote:
>
> From: Keith Busch <kbusch@kernel.org>
>
> Changes from v3:
>
>  - Allowed 128b opcodes on both big and mixed SQ's
>
>  - Added additional comments for clarity
>
>  - Commit message fixups
>
>  - Moved the uring specific entry size fucntion to the uring code.
>
> Keith Busch (1):
>   io_uring: add support for IORING_SETUP_SQE_MIXED
>
>  include/uapi/linux/io_uring.h |  8 ++++++++
>  io_uring/fdinfo.c             | 34 +++++++++++++++++++++++++++-------
>  io_uring/io_uring.c           | 35 +++++++++++++++++++++++++++++++----
>  io_uring/io_uring.h           | 14 ++------------
>  io_uring/opdef.c              | 26 ++++++++++++++++++++++++++
>  io_uring/opdef.h              |  2 ++
>  io_uring/register.c           |  2 +-
>  io_uring/uring_cmd.c          | 17 +++++++++++++++--
>  8 files changed, 112 insertions(+), 26 deletions(-)
>
> --
> 2.47.3
>

       reply	other threads:[~2025-10-10 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251009143645.2659663-1-kbusch@meta.com>
2025-10-10 20:44 ` Caleb Sander Mateos [this message]
2025-10-13 17:39   ` [PATCHv4 0/1] io_uring: mixed submission queue entries sizes Jens Axboe

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='CADUfDZoJkk6a6Kx4=MAnPbQHycA5AXe=MUrPkuWV8fmjb=H3HQ@mail.gmail.com' \
    --to=csander@purestorage.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.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