From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, cphealy@gmail.com,
vivien.didelot@savoirfairelinux.com, andrew@lunn.ch
Subject: Re: [PATCH net-next v2 0/4] net: dsa: bcm_sf2: CFP support
Date: Sun, 29 Jan 2017 22:46:01 -0800 [thread overview]
Message-ID: <F1B63CEA-29D4-4BC7-9476-9D489E4A4FB9@gmail.com> (raw)
In-Reply-To: <20170129031325.21911-1-f.fainelli@gmail.com>
On January 28, 2017 7:13:21 PM PST, Florian Fainelli <f.fainelli@gmail.com> wrote:
>Hi all,
>
>This patch series adds support for the Broadcom Compact Field Processor
>(CFP)
>which is a classification and matching engine built into most Broadcom
>switches.
>
>We support that using ethtool::rxnfc because it allows all known uses
>cases from
>the users I support to work, and more importantly, it allows the
>selection of a
>target rule index, which is later used by e.g: offloading hardware,
>this is an
>essential feature that I could not find being supported with cls_* for
>instance.
David, this needs to be rebase against net-next/master after Vivien's changes. Will post an update tomorrow. Thanks!
--
Florian
next prev parent reply other threads:[~2017-01-30 6:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 3:13 [PATCH net-next v2 0/4] net: dsa: bcm_sf2: CFP support Florian Fainelli
2017-01-29 3:13 ` [PATCH net-next v2 1/4] net: dsa: Hook {get,set}_rxnfc ethtool operations Florian Fainelli
2017-01-29 3:13 ` [PATCH net-next v2 2/4] net: dsa: bcm_sf2: Configure traffic classes to queue mapping Florian Fainelli
2017-01-29 3:13 ` [PATCH net-next v2 3/4] net: dsa: bcm_sf2: Add CFP registers definitions Florian Fainelli
2017-01-29 3:13 ` [PATCH net-next v2 4/4] net: dsa: bcm_sf2: Add support for ethtool::rxnfc Florian Fainelli
2017-01-30 6:46 ` Florian Fainelli [this message]
2017-01-30 16:17 ` [PATCH net-next v2 0/4] net: dsa: bcm_sf2: CFP support David Miller
2017-01-30 16:11 ` David Miller
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=F1B63CEA-29D4-4BC7-9476-9D489E4A4FB9@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=cphealy@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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