DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1349] Traffic filtering when capturing packets
Date: Wed, 10 Jan 2024 09:24:33 +0000	[thread overview]
Message-ID: <bug-1349-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1349

            Bug ID: 1349
           Summary: Traffic filtering when capturing packets
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: dts
          Assignee: dev@dpdk.org
          Reporter: juraj.linkes@pantheon.tech
                CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
  Target Milestone: ---

We currently have a solid solution in the scatter test suite patch. The
filtering is not the main thrust of the patch so it doesn't provide a fully
fleshed out solution.

We should think about the following:
- The solution covers the main use cases, probably what's needed for labs,
- We must document what we're filtering and warn that if a setup deviates (e.g.
there's extra traffic that's not going to be filtered) there could be related
test failures,
    - Related to the above, we could add a config option for extra default
filtering.
- The solution must be abstracted properly so it's easily implementable for all
capturing traffic generators.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3216 bytes --]

             reply	other threads:[~2024-01-10  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10  9:24 bugzilla [this message]
2024-02-15 14:55 ` [DPDK/DTS Bug " bugzilla

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=bug-1349-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).