Issues around packet capture when secondary process is doing rx/tx
Stephen Hemminger
stephen at networkplumber.org
Mon Jan 8 18:02:55 CET 2024
On Mon, 8 Jan 2024 15:13:25 +0000
Konstantin Ananyev <konstantin.ananyev at 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.
More information about the dev
mailing list