public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: vitalif@yourcmc.ru
To: "Pavel Begunkov" <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: io_uring zero-copy send test results
Date: Sat, 05 Apr 2025 21:46:13 +0000	[thread overview]
Message-ID: <37b5fd439fc2af5b3d8ffb0bd0c8277d@yourcmc.ru> (raw)
In-Reply-To: <5ce812ab-29a6-4132-a067-27ea27895940@gmail.com>

> fwiw, -z1 -b1 is the default, i.e. zc and fixed buffers

Yes, I know. :-) that's why I re-ran tests with -b 0 the second time.

> Sounds like another case of iommu being painfully slow. The difference
> is that while copying normal sends coalesce data into nice big contig
> buffers, but zerocopy has to deal with whatever pages it's given. That's
> 32KB vs 4KB, and the worst case scenario you get 8x more frags (and skbs)
> and 8x iommu mappings for zerocopy.

Problem is that on EPYC it's slow even with 64k buffers. Being slow is rather expectable with 4k buffers, but 64k...

> Try huge pages and see if it helps, it's -l1 in the benchmark. I can
> also take a look at adding pre-mapped buffers again.
> 
> Perf profiles would also be useful to have if you can grab and post
> them.

I.e. flamegraphs?

  parent reply	other threads:[~2025-04-05 21:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-05 16:58 io_uring zero-copy send test results vitalif
2025-04-05 18:11 ` Pavel Begunkov
2025-04-05 21:46 ` vitalif [this message]
2025-04-06 21:54   ` Pavel Begunkov
2025-04-06 21:08 ` vitalif
2025-04-06 22:01   ` Pavel Begunkov
2025-04-08 12:43   ` vitalif
2025-04-09  9:24     ` Pavel Begunkov
2025-04-18  8:50     ` vitalif

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=37b5fd439fc2af5b3d8ffb0bd0c8277d@yourcmc.ru \
    --to=vitalif@yourcmc.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox