All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCH liburing 0/3] sendzc test improvements
Date: Wed, 1 Mar 2023 13:00:17 -0700	[thread overview]
Message-ID: <c8842e6d-4ce6-75f5-5ca0-c77fa23290db@kernel.dk> (raw)
In-Reply-To: <cover.1677686850.git.asml.silence@gmail.com>

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:

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

-- 
Jens Axboe



  parent reply	other threads:[~2023-03-01 20:00 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 ` Jens Axboe [this message]
2023-03-01 20:31   ` [PATCH liburing 0/3] sendzc test improvements Pavel Begunkov

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=c8842e6d-4ce6-75f5-5ca0-c77fa23290db@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=io-uring@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.