From: Jens Axboe <[email protected]>
To: [email protected], [email protected],
[email protected], [email protected]
Cc: [email protected]
Subject: Re: [PATCH v4 00/12] add large CQE support for io-uring
Date: Tue, 26 Apr 2022 16:58:34 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Tue, 26 Apr 2022 11:21:22 -0700, Stefan Roesch wrote:
> This adds the large CQE support for io-uring. Large CQE's are 16 bytes longer.
> To support the longer CQE's the allocation part is changed and when the CQE is
> accessed.
>
> The allocation of the large CQE's is twice as big, so the allocation size is
> doubled. The ring size calculation needs to take this into account.
>
> [...]
Applied, thanks!
[01/12] io_uring: support CQE32 in io_uring_cqe
commit: 5c8bcc8e97123e3e68a6b1aa4c3eb6c5d5b9d174
[02/12] io_uring: store add. return values for CQE32
commit: 04c3f8c8deae29e184d54b2cd815f39fd46c6b2e
[03/12] io_uring: change ring size calculation for CQE32
commit: 9291ac41fda10ba7e80fc2147ca39a3b1d130ef9
[04/12] io_uring: add CQE32 setup processing
commit: bc6bda624e953fcf42c6075fe35a219ce6df4bc4
[05/12] io_uring: add CQE32 completion processing
commit: 22b76e8c5fd312701a1827b970230ee66aa24f69
[06/12] io_uring: modify io_get_cqe for CQE32
commit: 771c7f07faf909b9993fd5e42581c8c82531fb58
[07/12] io_uring: flush completions for CQE32
commit: b8e5029ed965c01066009bcb172c082b60ff436c
[08/12] io_uring: overflow processing for CQE32
commit: 3ee1cd786a668ba2a6e8dfefacb8f29e1d995c12
[09/12] io_uring: add tracing for additional CQE32 fields
commit: 225afd24978b55a771660fb4c6ad90cac75e7da8
[10/12] io_uring: support CQE32 in /proc info
commit: 41a971975a3ae2b498b9f5ecad34c34280f0ffdc
[11/12] io_uring: enable CQE32
commit: bb30aab40bcb6e9b80321615a2847a9491c95bf9
[12/12] io_uring: support CQE32 for nop operation
commit: 0fde61fe729221b43d9c8374cb57e571f4fb2a16
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-04-26 22:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 18:21 [PATCH v4 00/12] add large CQE support for io-uring Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 01/12] io_uring: support CQE32 in io_uring_cqe Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 02/12] io_uring: store add. return values for CQE32 Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 03/12] io_uring: change ring size calculation " Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 04/12] io_uring: add CQE32 setup processing Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 05/12] io_uring: add CQE32 completion processing Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 06/12] io_uring: modify io_get_cqe for CQE32 Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 07/12] io_uring: flush completions " Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 08/12] io_uring: overflow processing " Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 09/12] io_uring: add tracing for additional CQE32 fields Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 10/12] io_uring: support CQE32 in /proc info Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 11/12] io_uring: enable CQE32 Stefan Roesch
2022-04-26 18:21 ` [PATCH v4 12/12] io_uring: support CQE32 for nop operation Stefan Roesch
2022-04-26 22:58 ` 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=165101391469.210637.11826028295180623775.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[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