From: Roberts Tyrion <tyrion.roberts@gmail.com>
To: xdp-newbies@vger.kernel.org
Subject: How to use AF_XDP in media connections
Date: Wed, 19 Jan 2022 10:18:50 +0800 [thread overview]
Message-ID: <CABJTkezEc99OmEBMbnOq901gpXmUfYXUzToJXTDZQSdTseTnmA@mail.gmail.com> (raw)
Hi XDP experts,
Recently our team is trying to use AF_XDP to improve our socket
performance in media servers, which will spend 50%+ CPU resources in
socket send and recv functions. However, we still hear the different
voices that VPP/DPDK is one better option. I read many documents, and
found that if applications don’t attach packages, DPDK is better, and
if applications will process packages, XDP will approach the
performance of DPDK. For our applications, servers will create
hundreds of sockets to receive h264 streams, and send out these
streams into the different sockets. Based on the above descriptions,
do you think which solution is better one?
Another question is about AF_XDP usage: by this document,
https://www.kernel.org/doc/html/latest/networking/af_xdp.html
We need to use ethtool to map the ingress port and egress port, but
our application can create socket connections randomly, how to use
af_xdp to resolve this problem.
reply other threads:[~2022-01-19 2:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABJTkezEc99OmEBMbnOq901gpXmUfYXUzToJXTDZQSdTseTnmA@mail.gmail.com \
--to=tyrion.roberts@gmail.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 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).