From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Qiongwen Xu <qx51@cs.rutgers.edu>,
Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: "brouer@redhat.com" <brouer@redhat.com>,
Srinivas Narayana Ganapathy <sn624@cs.rutgers.edu>,
Tariq Toukan <tariqt@nvidia.com>,
"xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>
Subject: Re: Question about xdp: how to figure out the throughput is limited by pcie
Date: Thu, 13 Apr 2023 13:16:07 +0200 [thread overview]
Message-ID: <87fs94118o.fsf@toke.dk> (raw)
In-Reply-To: <7C8EC844-D2DF-4980-A178-30E2719E3575@cs.rutgers.edu>
Qiongwen Xu <qx51@cs.rutgers.edu> writes:
> Hi Jesper,
>
> Thanks for the detailed reply and sharing these helpful
> materials/papers with us!
(Please don't top post on the mailing list).
> After enabling rx_cqe_compress, the throughput in our experiment increases from
> 70+Mpps to 85 Mpps. We also tried to use the counter "rx_discards_phy". The counter
> increases in both cpu-limited and pcie-limited experiments, i.e., in the experiment
> which is only cpu-limited can also increase the counter. We are looking for any
> counter that can separate cpu- and pcie-limited cases. Regarding the [pcie-bench] tool,
> unfortunately, we are not able to use it, as it requires fpga hardware.
Well, are your CPUs being maxed out? IIRC it was pretty obvious that
they weren't when we were running those tests, so just looking at
something like 'mpstat' should give you a hint. For more detailed
analysis you can use 'perf' to see exactly where the CPU is spending its
time.
-Toke
next prev parent reply other threads:[~2023-04-13 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 1:46 Question about xdp: how to figure out the throughput is limited by pcie Qiongwen Xu
2023-04-09 15:44 ` Jesper Dangaard Brouer
[not found] ` <CH2PR14MB3657EF09F9A2BE7C08E4C9DBE3989@CH2PR14MB3657.namprd14.prod.outlook.com>
2023-04-13 2:54 ` Qiongwen Xu
2023-04-13 11:16 ` Toke Høiland-Jørgensen [this message]
2023-04-13 11:30 ` Jesper Dangaard Brouer
2023-04-13 11:59 ` Jesper Dangaard Brouer
2023-04-13 20:11 ` Andi Kleen
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=87fs94118o.fsf@toke.dk \
--to=toke@redhat.com \
--cc=brouer@redhat.com \
--cc=jbrouer@redhat.com \
--cc=qx51@cs.rutgers.edu \
--cc=sn624@cs.rutgers.edu \
--cc=tariqt@nvidia.com \
--cc=xdp-newbies@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.