From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH liburing for-next 0/5] expand send / zc tests
Date: Wed, 19 Oct 2022 19:26:24 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 20 Oct 2022 02:49:50 +0100, Pavel Begunkov wrote:
> Patch 4 adds sendmsg testing with various iov lengths and configurations.
> Patch 5 tests IORING_RECVSEND_POLL_FIRST. And patch 3 enables same testing
> for non-zerocopy sends as we currently have poor coverage.
>
> Pavel Begunkov (5):
> tests: improve zc cflags handling
> tests: pass params in a struct
> tests: add non-zc tests in send-zerocopy.c
> tests: add tests for retries with long iovec
> tests: test poll_first
>
> [...]
Applied, thanks!
[1/5] tests: improve zc cflags handling
(no commit info)
[2/5] tests: pass params in a struct
(no commit info)
[3/5] tests: add non-zc tests in send-zerocopy.c
(no commit info)
[4/5] tests: add tests for retries with long iovec
(no commit info)
[5/5] tests: test poll_first
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-10-20 2:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 1:49 [PATCH liburing for-next 0/5] expand send / zc tests Pavel Begunkov
2022-10-20 1:49 ` [PATCH liburing for-next 1/5] tests: improve zc cflags handling Pavel Begunkov
2022-10-20 1:49 ` [PATCH liburing for-next 2/5] tests: pass params in a struct Pavel Begunkov
2022-10-20 1:49 ` [PATCH liburing for-next 3/5] tests: add non-zc tests in send-zerocopy.c Pavel Begunkov
2022-10-20 1:49 ` [PATCH liburing for-next 4/5] tests: add tests for retries with long iovec Pavel Begunkov
2022-10-20 1:49 ` [PATCH liburing for-next 5/5] tests: test poll_first Pavel Begunkov
2022-10-20 2:26 ` 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=166623278402.153320.17837453222365546552.b4-ty@kernel.dk \
[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