From: Kanchan Joshi <joshi.k@samsung.com>
To: Breno Leitao <leitao@debian.org>
Cc: io-uring@vger.kernel.org, linux-nvme@lists.infradead.org,
asml.silence@gmail.com, axboe@kernel.dk, leit@fb.com,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
sagi@grimberg.me, hch@lst.de, kbusch@kernel.org,
ming.lei@redhat.com
Subject: Re: [PATCH v2 0/3] io_uring: Pass the whole sqe to commands
Date: Fri, 21 Apr 2023 17:46:05 +0530 [thread overview]
Message-ID: <20230421121605.GA30924@green245> (raw)
In-Reply-To: <20230421114440.3343473-1-leitao@debian.org>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
On Fri, Apr 21, 2023 at 04:44:37AM -0700, Breno Leitao wrote:
>These three patches prepare for the sock support in the io_uring cmd, as
>described in the following RFC:
>
> https://lore.kernel.org/lkml/20230406144330.1932798-1-leitao@debian.org/
>
>Since the support linked above depends on other refactors, such as the sock
>ioctl() sock refactor[1], I would like to start integrating patches that have
>consensus and can bring value right now. This will also reduce the patchset
>size later.
>
>Regarding to these three patches, they are simple changes that turn
>io_uring cmd subsystem more flexible (by passing the whole SQE to the
>command), and cleaning up an unnecessary compile check.
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2023-04-21 12:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230421114703epcas5p37cd0ddb29674d8f3d5fe2f1fa494d1f0@epcas5p3.samsung.com>
2023-04-21 11:44 ` [PATCH v2 0/3] io_uring: Pass the whole sqe to commands Breno Leitao
2023-04-21 11:44 ` [PATCH v2 1/3] io_uring: Create a helper to return the SQE size Breno Leitao
2023-04-24 7:19 ` Christoph Hellwig
2023-04-21 11:44 ` [PATCH v2 2/3] io_uring: Pass whole sqe to commands Breno Leitao
2023-04-24 7:23 ` Christoph Hellwig
2023-04-21 11:44 ` [PATCH v2 3/3] io_uring: Remove unnecessary BUILD_BUG_ON Breno Leitao
2023-04-24 7:23 ` Christoph Hellwig
2023-04-28 17:27 ` Jens Axboe
2023-04-21 12:16 ` Kanchan Joshi [this message]
2023-04-28 17:28 ` [PATCH v2 0/3] io_uring: Pass the whole sqe to commands Jens Axboe
2023-04-30 14:39 ` Breno Leitao
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=20230421121605.GA30924@green245 \
--to=joshi.k@samsung.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@kernel.org \
--cc=leit@fb.com \
--cc=leitao@debian.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.com \
--cc=sagi@grimberg.me \
/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.