From: Florian Fainelli <f.fainelli@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, andrew@lunn.ch,
vivien.didelot@savoirfairelinux.com, pablo@netfilter.org
Subject: Re: [PATCH net-next 0/5] net: dsa: bcm_sf2: Store rules in lists
Date: Tue, 6 Nov 2018 15:09:04 -0800 [thread overview]
Message-ID: <b7ebd795-3328-ecb2-cb02-cf8fa51e1570@gmail.com> (raw)
In-Reply-To: <20181106.150619.2176282733992923198.davem@davemloft.net>
On 11/6/18 3:06 PM, David Miller wrote:
> From: Florian Fainelli <f.fainelli@gmail.com>
> Date: Tue, 6 Nov 2018 12:58:36 -0800
>
>> Hi all,
>>
>> This patch series changes the bcm-sf2 driver to keep a copy of the
>> inserted rules as opposed to using the HW as a storage area for a number
>> of reasons:
>>
>> - this helps us with doing duplicate rule detection in a faster way, it
>> would have required a full rule read before
>>
>> - this helps with Pablo's on-going work to convert ethtool_rx_flow_spec
>> to a more generic flow rule structure by having fewer code paths to
>> convert to the new structure/helpers
>>
>> - we need to cache copies to restore them during drive resumption,
>> because depending on the low power mode the system has entered, the
>> switch may have lost all of its context
>
> Looks good to me, series applied and build testing right now.
>
> I will say that the ethtool flow spec comparison should probably
> eventually be broken out into a helper function places somewhere
> common. It's very likely this approach, and thus the helper, can
> be used by other drivers in a similar situation.
Sure, that could be done, I will check with Pablo how he wants to
approach that as well since he is reworking how flow rules are
represented. Thanks!
--
Florian
prev parent reply other threads:[~2018-11-07 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 20:58 [PATCH net-next 0/5] net: dsa: bcm_sf2: Store rules in lists Florian Fainelli
2018-11-06 20:58 ` [PATCH net-next 1/5] net: dsa: bcm_sf2: Keep copy of inserted rules Florian Fainelli
2018-11-06 20:58 ` [PATCH net-next 2/5] net: dsa: bcm_sf2: Split rule handling from HW operation Florian Fainelli
2018-11-06 20:58 ` [PATCH net-next 3/5] net: dsa: bcm_sf2: Restore CFP rules during system resume Florian Fainelli
2018-11-06 20:58 ` [PATCH net-next 4/5] net: dsa: bcm_sf2: Get rid of unmarshalling functions Florian Fainelli
2018-11-06 20:58 ` [PATCH net-next 5/5] net: systemport: Restore Broadcom tag match filters upon resume Florian Fainelli
2018-11-06 23:06 ` [PATCH net-next 0/5] net: dsa: bcm_sf2: Store rules in lists David Miller
2018-11-06 23:09 ` Florian Fainelli [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=b7ebd795-3328-ecb2-cb02-cf8fa51e1570@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).