XDP-Newbies Archive mirror
 help / color / mirror / Atom feed
From: Qiongwen Xu <qx51@cs.rutgers.edu>
To: "xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>
Cc: Srinivas Narayana Ganapathy <sn624@cs.rutgers.edu>
Subject: Question about xdp: how to figure out the throughput is limited by pcie
Date: Fri, 7 Apr 2023 01:46:24 +0000	[thread overview]
Message-ID: <CH2PR14MB365761EDE0FB656784E79728E3969@CH2PR14MB3657.namprd14.prod.outlook.com> (raw)

Dear XDP experts,

Hope this email finds you well!

I am a PhD student at Rutgers. Recently, I have been reading the XDP paper "The eXpress Data Path: Fast Programmable Packet Processing in the Operating System Kernel". In section 4.1 and 4.3, you mention the throughputs of xdp programs (packet drop and packet forwarding) are limited by the PCIe (e.g., "Both scale their performance linearly until they approach the global performance limit of the PCI bus"). I am curious about how you figured out it was the PCIe limitation. Is there any tool or method to check this?

Looking forward to your reply!

Thanks,
Qiongwen Xu



             reply	other threads:[~2023-04-07  1:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07  1:46 Qiongwen Xu [this message]
2023-04-09 15:44 ` Question about xdp: how to figure out the throughput is limited by pcie 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
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=CH2PR14MB365761EDE0FB656784E79728E3969@CH2PR14MB3657.namprd14.prod.outlook.com \
    --to=qx51@cs.rutgers.edu \
    --cc=sn624@cs.rutgers.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).