From: Fuji Nafiul <nafiul.fuji@gmail.com>
To: users@dpdk.org, dev@dpdk.org
Subject: High packet capturing rate in DPDK enabled port
Date: Sun, 5 May 2024 13:09:42 +0600 [thread overview]
Message-ID: <CA+3hWeyzcQRffMK8nTmh5mRMu=3WmqOd1jM5iBo-zUC6Bwq52A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
I have a DPDK-enabled port (Linux server) that serves around 5,000-50,000
concurrent calls, per packet size of 80 bytes to 200 bytes. so in peak
time, I require packet capture + file writing speed of around 1GByte/s or 8
Gbit/sec (at least 0.5Gbyte/s is expected). dpdk official packet capture
example project "dpdk-dumpcap"'s documentation says it has a capability of
around 10MByte/s which is far less than required. I implemented a simple
packet capture and pcap writing code which was able to dump
around 5000-7000 concurrent call data where I used 1 core and 1 single ring
of size 4096, and this was all integrated into actual media code (didn't
use librte_pdump, simply copied to separate rte_ring after capturing
through rte_eth_rx_burst() and before sending through rte_eth_tx_burst() ).
I know I can launch this multiple cores and with multiple rings and so on
but is there any current project which already does this?
I found a third-party project named "dpdkcap" which says it can support up
to 10Gbit/s. Has anyone used it and what's the review?
Or, should I modify the "dpdk-dumpcap" project to my need to
implement multicore and multi-ring support so I can extend the capability?
Thanks in advance
[-- Attachment #2: Type: text/html, Size: 1357 bytes --]
next reply other threads:[~2024-05-05 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 7:09 Fuji Nafiul [this message]
2024-05-05 16:02 ` Stephen Hemminger
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='CA+3hWeyzcQRffMK8nTmh5mRMu=3WmqOd1jM5iBo-zUC6Bwq52A@mail.gmail.com' \
--to=nafiul.fuji@gmail.com \
--cc=dev@dpdk.org \
--cc=users@dpdk.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 NNTP newsgroup(s).