From: Jens Axboe <[email protected]>
To: Christoph Hellwig <[email protected]>
Cc: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: io_uring req flags cleanups
Date: Tue, 20 Jun 2023 09:36:55 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Tue, 20 Jun 2023 13:32:27 +0200, Christoph Hellwig wrote:
> while looking at the NOWAIT flag handling I found various bits of code
> related to it pretty convoluted and confusing. This series tries to
> clean them up, let me know what you think.
>
> Diffstat:
> cancel.c | 5 +----
> filetable.c | 11 ++++-------
> filetable.h | 28 +++++++++++++++++-----------
> io_uring.c | 41 ++++++++++-------------------------------
> io_uring.h | 5 -----
> msg_ring.c | 4 +---
> rsrc.c | 8 ++++----
> rw.c | 4 ++--
> 8 files changed, 39 insertions(+), 67 deletions(-)
>
> [...]
Applied, thanks!
[1/8] io_uring: remove __io_file_supports_nowait
commit: b9a6c9459a5aec7bfd9b763554d15148367f1806
[2/8] io_uring: remove the mode variable in io_file_get_flags
commit: 53cfd5cea7f36bac7f3d45de4fea77e0c8d57aee
[3/8] io_uring: remove a confusing comment above io_file_get_flags
commit: b57c7cd1c17616ae9db5614525ba703f384afd05
[4/8] io_uring: remove io_req_ffs_set
commit: 3beed235d1a1d0a4ab093ab67ea6b2841e9d4fa2
[5/8] io_uring: return REQ_F_ flags from io_file_get_flags
commit: 8487f083c6ff6e02b2ec14f22ef2b0079a1b6425
[6/8] io_uring: use io_file_from_index in __io_sync_cancel
commit: 60a666f097a8d722a3907925d21e363add289c8c
[7/8] io_uring: use io_file_from_index in io_msg_grab_file
commit: f432c8c8c12b84c5465b1ffddb6feb7d6b19c1ca
[8/8] io_uring: add helpers to decode the fixed file file_ptr
commit: 4bfb0c9af832a182a54e549123a634e0070c8d4f
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-06-20 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 11:32 io_uring req flags cleanups Christoph Hellwig
2023-06-20 11:32 ` [PATCH 1/8] io_uring: remove __io_file_supports_nowait Christoph Hellwig
2023-06-20 11:32 ` [PATCH 2/8] io_uring: remove the mode variable in io_file_get_flags Christoph Hellwig
2023-06-20 11:32 ` [PATCH 3/8] io_uring: remove a confusing comment above io_file_get_flags Christoph Hellwig
2023-06-20 11:32 ` [PATCH 4/8] io_uring: remove io_req_ffs_set Christoph Hellwig
2023-06-20 11:32 ` [PATCH 5/8] io_uring: return REQ_F_ flags from io_file_get_flags Christoph Hellwig
2023-06-20 11:32 ` [PATCH 6/8] io_uring: use io_file_from_index in __io_sync_cancel Christoph Hellwig
2023-06-20 11:32 ` [PATCH 7/8] io_uring: use io_file_from_index in io_msg_grab_file Christoph Hellwig
2023-06-20 11:32 ` [PATCH 8/8] io_uring: add helpers to decode the fixed file file_ptr Christoph Hellwig
2023-06-20 15:36 ` Jens Axboe [this message]
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=168727541583.3665205.11063729024991422548.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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