From: Wenwen Chen <[email protected]>
To: [email protected]
Cc: [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH v6] io_uring: releasing CPU resources when polling
Date: Tue, 9 Jul 2024 16:59:41 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Sorry for bad format, here is the test results maybe looks better:
Performance
-------------------------------------------------------------------------------------
write read randwrite randread
regular poll BW=3939MiB/s BW=6596MiB/s IOPS=190K IOPS=526K
IRQ BW=3927MiB/s BW=6567MiB/s IOPS=181K IOPS=216K
hybrid poll BW=3933MiB/s BW=6600MiB/s IOPS=190K IOPS=390K(suboptimal)
-------------------------------------------------------------------------------------
CPU Utilization
-------------------------------------------------------------------------------------
write read randwrite randread
regular poll 100% 100% 100% 100%
IRQ 38% 53% 100% 100%
hybrid poll 76% 32% 70% 85%
-------------------------------------------------------------------------------------
--
hexue
next prev parent reply other threads:[~2024-07-09 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240709081627epcas5p3033c01e4816310394f8efbbd4b43cfd0@epcas5p3.samsung.com>
2024-07-09 8:16 ` [PATCH v6] io_uring: releasing CPU resources when polling hexue
[not found] ` <CGME20240709085955epcas5p267fabe2536dc064f6595df1b46463a1e@epcas5p2.samsung.com>
2024-07-09 8:59 ` Wenwen Chen [this message]
[not found] ` <CGME20240709092454epcas5p4b4ffaa306b3ce12ec57ce4eb19e08572@epcas5p4.samsung.com>
2024-07-09 9:24 ` hexue
2024-07-09 9:29 [PATCH v6 RESEND] " hexue
[not found] ` <CGME20240718100113epcas5p255acf51a58cf410d5d0e8cffbca41994@epcas5p2.samsung.com>
2024-07-18 10:01 ` [PATCH V6] " hexue
2024-07-19 19:05 ` Jens Axboe
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] \
[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