From: Thomas Monjalon <thomas@monjalon.net>
To: Owen Hilyard <ohilyard@iol.unh.edu>
Cc: dev@dpdk.org, dts@dpdk.org, qi.z.zhang@intel.com,
matan@mellanox.com, stephen@networkplumber.org,
jerinj@marvell.com, suanmingm@mellanox.com,
kalesh-anakkur.purayil@broadcom.com, pbhagavatula@marvell.com,
david.marchand@redhat.com, dekelp@mellanox.com,
bruce.richardson@intel.com, ferruh.yigit@intel.com,
mk@semihalf.com, viacheslavo@mellanox.com
Subject: Re: [dpdk-dev] Multicast MAC Filter Test Case
Date: Fri, 03 Jul 2020 11:11:57 +0200 [thread overview]
Message-ID: <13850469.gVNdlFUnev@thomas> (raw)
In-Reply-To: <CAHx6DYAZoPsxSy3O6Tt9VXnEsoZyB9LTmeJxqUz2n5T8rQXhpw@mail.gmail.com>
02/07/2020 15:26, Owen Hilyard:
> Hello Everyone,
>
> I wanted to see if anyone had any suggestions regarding testing the
> multicast mac filter. My current plan is to send a frame and check it's not
> received, then add the multicast address to the filter and send another
> frame, checking that it is received. Suggestions of other test cases for
> this feature are also welcome.
You can check that unicast is still working.
You can check bradcast behaviour.
You can test different ranges and flags of multicast addresses.
I wonder which kind of environment or configuration change
could have a side effect on multicast.
Any ideas about more complex test cases?
prev parent reply other threads:[~2020-07-03 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 13:26 Owen Hilyard
2020-07-03 9:11 ` Thomas Monjalon [this message]
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=13850469.gVNdlFUnev@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=dts@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=matan@mellanox.com \
--cc=mk@semihalf.com \
--cc=ohilyard@iol.unh.edu \
--cc=pbhagavatula@marvell.com \
--cc=qi.z.zhang@intel.com \
--cc=stephen@networkplumber.org \
--cc=suanmingm@mellanox.com \
--cc=viacheslavo@mellanox.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).