From: Stephen Hemminger <stephen@networkplumber.org>
To: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"arshdeep.kaur@intel.com" <arshdeep.kaur@intel.com>,
"Gowda, Sandesh" <sandesh.gowda@intel.com>,
Reshma Pattan <reshma.pattan@intel.com>
Subject: Re: Issues around packet capture when secondary process is doing rx/tx
Date: Mon, 8 Jan 2024 09:02:55 -0800 [thread overview]
Message-ID: <20240108090255.74d13f9d@hermes.local> (raw)
In-Reply-To: <5c28d2a26f5142c3a509cc8bda2fca75@huawei.com>
On Mon, 8 Jan 2024 15:13:25 +0000
Konstantin Ananyev <konstantin.ananyev@huawei.com> wrote:
> >
> > 2. Replace use of rx/tx callback in pdump with change to rte_ethdev to have
> > a capture flag. (i.e. don't use indirection). Likely ABI problems.
> > Basically, ignore the rx/tx callback mechanism. This is my preferred
> > solution.
>
> It is not only the capture flag, it is also what to do with the captured packets
> (copy? If yes, then where to? examine? drop?, do something else?).
> It is probably not the best choice to add all these things into ethdev API.
The part that pdump does is trivial, it just copies and puts in ring.
This will work from any process.
next prev parent reply other threads:[~2024-01-08 17:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 1:59 Stephen Hemminger
2024-01-08 10:41 ` Morten Brørup
2024-04-03 11:43 ` Ferruh Yigit
2024-01-08 15:13 ` Konstantin Ananyev
2024-01-08 17:02 ` Stephen Hemminger [this message]
2024-01-08 17:55 ` Stephen Hemminger
2024-01-09 23:06 ` Stephen Hemminger
2024-01-09 23:07 ` Stephen Hemminger
2024-04-03 12:11 ` Ferruh Yigit
2024-01-10 20:11 ` Konstantin Ananyev
2024-04-03 12:20 ` Ferruh Yigit
2024-04-04 13:26 ` Konstantin Ananyev
2024-04-04 14:28 ` Ferruh Yigit
2024-04-04 15:21 ` Stephen Hemminger
2024-04-04 16:18 ` Konstantin Ananyev
2024-04-03 0:14 ` Stephen Hemminger
2024-04-03 11:42 ` Ferruh Yigit
2024-01-09 1:30 ` Honnappa Nagarahalli
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=20240108090255.74d13f9d@hermes.local \
--to=stephen@networkplumber.org \
--cc=arshdeep.kaur@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=reshma.pattan@intel.com \
--cc=sandesh.gowda@intel.com \
/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).