From: David Miller <davem@davemloft.net>
To: maxime.chevallier@bootlin.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, antoine.tenart@bootlin.com,
miquel.raynal@bootlin.com, gregory.clement@bootlin.com,
mw@semihalf.com, ymarkman@marvell.com, nadavh@marvell.com,
stefanc@marvell.com
Subject: Re: [PATCH net-next 0/2] net: mvpp2: Add Unicast filtering capabilities
Date: Wed, 07 Mar 2018 15:54:10 -0500 (EST) [thread overview]
Message-ID: <20180307.155410.724183535049256132.davem@davemloft.net> (raw)
In-Reply-To: <20180307141804.348-1-maxime.chevallier@bootlin.com>
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
Date: Wed, 7 Mar 2018 15:18:02 +0100
> This series adds unicast filtering support to the Marvell PPv2 controller.
>
> This is implemented using the header parser cababilities of the PPv2,
> which allows for generic packet filtering based on matching patterns in
> the packet headers.
>
> PPv2 controller only has 256 of these entries, and we need to share them
> with other features, such as VLAN filtering.
>
> For each interface, we have 5 entries dedicated to unicast filtering (the
> controller's own address, and 4 other), and 21 to multicast filtering.
>
> When this number is reached, the controller switches to unicast or
> multicast promiscuous mode.
>
> The first patch reworks the function that adds and removes addresses to the
> filter. This is preparatory work to ease UC filter implementation.
>
> The second patch adds the UC filtering feature.
Series applied, thanks.
prev parent reply other threads:[~2018-03-07 20:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 14:18 [PATCH net-next 0/2] net: mvpp2: Add Unicast filtering capabilities Maxime Chevallier
2018-03-07 14:18 ` [PATCH net-next 1/2] net: mvpp2: Simplify MAC filtering function parameters Maxime Chevallier
2018-03-07 14:18 ` [PATCH net-next 2/2] net: mvpp2: Add support for unicast filtering Maxime Chevallier
2018-03-07 20:54 ` David Miller [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=20180307.155410.724183535049256132.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=antoine.tenart@bootlin.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=stefanc@marvell.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=ymarkman@marvell.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).