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: Fri, 18 Apr 2025 08:50:45 +0000	[thread overview]
Message-ID: <2ca2145ee741969708e399573af269e9@yourcmc.ru> (raw)
In-Reply-To: <c20c9c4c-19c4-47fe-b9d7-b4e8dde766bc@gmail.com>

Hi,

> Nice! Is ~2400 MB/s a hardware bottleneck? Seems like the t-put
> converges to that, while I'd expect the gap to widen as we increase
> the size to 64K.

I'm not sure, it doesn't seem so, these servers are connected with a 2x100G bonded connection. Iperf -P8 (8 threads) shows 100 Gbit/s...

>> Didn't have time to repeat tests with perf on those servers yet, but I can check dmesg logs. In the
>> default iommu mode, /sys/class/iommu is empty and dmesg includes the following lines:
>> DMAR-IR: IOAPIC id 8 under DRHD base 0x9b7fc000 IOMMU 9
>> iommu: Default domain type: Translated
>> iommu: DMA domain TLB invalidation policy: lazy mode
>> With iommu=pt, dmesg has:
>> DMAR-IR: IOAPIC id 8 under DRHD base 0x9b7fc000 IOMMU 9
>> iommu: Default domain type: Passthrough (set via kernel command line)

You're probably right, it was just a random mistake, I repeated the test again with iommu=pt and without it and the new results are very close to each other, and iommu=pt result is even slightly better. So never mind :)

Xeon Gold 6342 + Mellanox ConnectX-6 Dx + iommu=pt, run 2

           4096  8192  10000  12000  16384  32768  65435
zc MB/s    2681  2947  2927   2935   2949   2947   2945
zc CPU     99%   66%   41%    48%    22%    13%    11%
send MB/s  2950  2951  2950   2950   2949   2950   2949
send CPU   48%   35%   31%    34%    28%    29%    25%

Xeon Gold 6342 + Mellanox ConnectX-6 Dx, run 2

           4096  8192  10000  12000  16384  32768  65435
zc MB/s    2262  2948  2925   2935   2946   2947   2947
zc CPU     99%   52%   60%    44%    24%    17%    17%
send MB/s  2950  2949  2950   2950   2950   2950   2950
send CPU   48%   38%   36%    31%    33%    26%    29%

      reply	other threads:[~2025-04-18  8:58 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
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 [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=2ca2145ee741969708e399573af269e9@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