public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: [PATCH liburing 0/3] sendzc test improvements
Date: Wed, 1 Mar 2023 20:31:11 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 3/1/23 20:00, Jens Axboe wrote:
> On 3/1/23 9:10 AM, Pavel Begunkov wrote:
>> Add affinity, multithreading and the server
>>
>> Pavel Begunkov (3):
>>    examples/send-zc: add affinity / CPU pinning
>>    examples/send-zc: add multithreading
>>    examples/send-zc: add the receive part
>>
>>   examples/Makefile        |   3 +
>>   examples/send-zerocopy.c | 277 ++++++++++++++++++++++++++++++++++-----
>>   2 files changed, 249 insertions(+), 31 deletions(-)
> 
> This doesn't apply to the current tree, what am I missing? I
> don't see any send-zc changes since the last ones you did.
> First patch:

Don't know what that is, I'll resend later
  
> axboe@m1max ~/gi/liburing (master)> patch -p1 --dry-run < 1
> checking file examples/send-zerocopy.c
> Hunk #1 succeeded at 12 with fuzz 2.
> Hunk #2 FAILED at 51.
> Hunk #3 succeeded at 78 (offset -2 lines).
> Hunk #4 succeeded at 192 (offset -7 lines).
> Hunk #5 FAILED at 333.
> Hunk #6 succeeded at 360 with fuzz 2 (offset -14 lines).
> Hunk #7 succeeded at 382 (offset -14 lines).
> 2 out of 7 hunks FAILED
> 

-- 
Pavel Begunkov

      reply	other threads:[~2023-03-01 20:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 16:10 [PATCH liburing 0/3] sendzc test improvements Pavel Begunkov
2023-03-01 16:10 ` [PATCH liburing 1/3] examples/send-zc: add affinity / CPU pinning Pavel Begunkov
2023-03-01 16:10 ` [PATCH liburing 2/3] examples/send-zc: add multithreading Pavel Begunkov
2023-03-01 16:10 ` [PATCH liburing 3/3] examples/send-zc: add the receive part Pavel Begunkov
2023-03-01 20:00 ` [PATCH liburing 0/3] sendzc test improvements Jens Axboe
2023-03-01 20:31   ` 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] \
    /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