public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Dylan Yudaken <[email protected]>,
	"[email protected]" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [PATCH liburing 4/4] tests/zc: name buffer flavours
Date: Mon, 5 Sep 2022 16:17:37 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 9/5/22 16:00, Dylan Yudaken wrote:
> On Mon, 2022-09-05 at 15:21 +0100, Pavel Begunkov wrote:
>> Remove duplicating tests and pass a buf index instead of dozens of
>> flags to specify the buffer we want to use.
>>
>> Signed-off-by: Pavel Begunkov <[email protected]>
>> ---
>>   test/send-zerocopy.c | 60 +++++++++++++++++++++++-------------------
>> --
>>   1 file changed, 32 insertions(+), 28 deletions(-)
>>
>> diff --git a/test/send-zerocopy.c b/test/send-zerocopy.c
>> index bfe4cf7..2efbcf9 100644
>> --- a/test/send-zerocopy.c
>> +++ b/test/send-zerocopy.c
>> @@ -51,8 +51,16 @@
>>          #define ARRAY_SIZE(a) (sizeof(a)/sizeof((a)[0]))
>>   #endif
>>   
>> +enum {
>> +       BUF_T_NORMAL,
>> +       BUF_T_SMALL,
>> +       BUF_T_NONALIGNED,
>> +       BUF_T_LARGE,
>> +       __BUT_T_MAX,
> 
> __BUF_T_MAX?

eh, should've been. I think I'll just kill it in a resend.

-- 
Pavel Begunkov

      reply	other threads:[~2022-09-05 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 14:21 [PATCH liburing 0/4] zc tests improvements Pavel Begunkov
2022-09-05 14:21 ` [PATCH liburing 1/4] tests/zc: move send size calc into do_test_inet_send Pavel Begunkov
2022-09-05 14:21 ` [PATCH liburing 2/4] tests/zc: use io_uring for rx Pavel Begunkov
2022-09-05 14:21 ` [PATCH liburing 3/4] tests/zc: fix udp testing Pavel Begunkov
2022-09-05 14:21 ` [PATCH liburing 4/4] tests/zc: name buffer flavours Pavel Begunkov
2022-09-05 15:00   ` Dylan Yudaken
2022-09-05 15:17     ` Pavel Begunkov [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 \
    [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