From: "Nicolson Ken (ニコルソン ケン)" <ken.nicolson@jp.panasonic.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Tapping a Tx port to access all the packets being Txed
Date: Thu, 11 Jan 2024 05:55:53 +0000 [thread overview]
Message-ID: <OSZPR01MB77486C84F5547C9846A1694BBC682@OSZPR01MB7748.jpnprd01.prod.outlook.com> (raw)
Hi all,
I'm wanting to basically tap a DPDK stream and for instance save all packets being Txed by a PMD to a separate file.
I know I could relatively easily modify an existing PMD to have two output ports, but is there either an existing PMD that does this, or a programmatic way to graft a second port onto an arbitrary PMD, or is there another simpler way that I haven't realised yet. As mbufs are already reference counted, I would hope, and require, that such a solution would be zero copy. RSS-friendly would also be a plus.
Thanks,
Ken
next reply other threads:[~2024-01-11 5:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 5:55 Nicolson Ken (ニコルソン ケン) [this message]
2024-01-11 17:04 ` 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=OSZPR01MB77486C84F5547C9846A1694BBC682@OSZPR01MB7748.jpnprd01.prod.outlook.com \
--to=ken.nicolson@jp.panasonic.com \
--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).