From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH liburing 0/7] test sends with huge pages
Date: Wed, 22 Feb 2023 09:54:04 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Tue, 21 Feb 2023 01:05:51 +0000, Pavel Begunkov wrote:
> Add huge pages support for zc send benchmark and huge pages
> tests in send-zerocopy.c.
>
> Pavel Begunkov (7):
> tests/send: don't use a constant for page size
> send: improve buffer iteration
> send: test send with hugetlb
> examples/zc: add a hugetlb option
> test/send: don't use SO_ZEROCOPY if not available
> tests/send: improve error reporting
> tests/send: sends with offsets
>
> [...]
Applied, thanks!
[1/7] tests/send: don't use a constant for page size
(no commit info)
[2/7] send: improve buffer iteration
(no commit info)
[3/7] send: test send with hugetlb
(no commit info)
[4/7] examples/zc: add a hugetlb option
(no commit info)
[5/7] test/send: don't use SO_ZEROCOPY if not available
(no commit info)
[6/7] tests/send: improve error reporting
(no commit info)
[7/7] tests/send: sends with offsets
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-02-22 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 1:05 [PATCH liburing 0/7] test sends with huge pages Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 1/7] tests/send: don't use a constant for page size Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 2/7] send: improve buffer iteration Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 3/7] send: test send with hugetlb Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 4/7] examples/zc: add a hugetlb option Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 5/7] test/send: don't use SO_ZEROCOPY if not available Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 6/7] tests/send: improve error reporting Pavel Begunkov
2023-02-21 1:05 ` [PATCH liburing 7/7] tests/send: sends with offsets Pavel Begunkov
2023-02-22 16:54 ` 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=167708484463.23363.15624381216996618725.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