From: Or Gerlitz <or.gerlitz@gmail.com>
To: Yevgeny Petrilin <yevgenyp@mellanox.co.il>
Cc: Roland Dreier <rdreier@cisco.com>,
netdev@vger.kernel.org, tziporet@mellanox.co.il,
liranl@mellanox.co.il, Alex Rosenbaum <alexr@voltaire.com>
Subject: Re: Re: [PATCH 18/23 v3] mlx4_core: Managing common port filters by
Date: Tue, 16 Feb 2010 08:53:47 +0200 [thread overview]
Message-ID: <15ddcffd1002152253g2426f3e9l33cdc6b862d7734c@mail.gmail.com> (raw)
In-Reply-To: <4B72EB6B.9000708@mellanox.co.il>
On Wed, Feb 10, 2010 at 7:22 PM, Yevgeny Petrilin
<yevgenyp@mellanox.co.il> wrote:
> On Sunday -10,January,-28163 09:59 PM, Or Gerlitz [or.gerlitz@gmail.com] wrote:
> The multicast bloom filter is a false-positive filter per port.
> All multicast packets go through the Multicast tables mechanism where every PF/VF is registered for every multicast address
okay, so the bloom filter is going and exact match is coming, understood.
>> As for the false-positive vlan filter, I understand that this means further filtering has to be applied by some driver. Where you
>> thinking on the 802q driver? what about the case where a VF driver is assigned a vlan, does the mlx4 VF code does filtering?
> The deal with the VLAN filter is similar, it includes all VIDs that some PF/VF requested.
So for a given VID, a unicast packet carrying it will be dispatched to
all the PFs/VFs which
have registered this VID? I guess this isn't the case, so please elaborate.
> We plan to add a MAC+VLAN filter implementation, that would cancel the need in this filter.
I'm still not clear in what level you expect the software filtering to happen
Or.
prev parent reply other threads:[~2010-02-16 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 17:22 Re: [PATCH 18/23 v3] mlx4_core: Managing common port filters by Yevgeny Petrilin
2010-02-16 6:53 ` Or Gerlitz [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=15ddcffd1002152253g2426f3e9l33cdc6b862d7734c@mail.gmail.com \
--to=or.gerlitz@gmail.com \
--cc=alexr@voltaire.com \
--cc=liranl@mellanox.co.il \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=tziporet@mellanox.co.il \
--cc=yevgenyp@mellanox.co.il \
/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).