[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE4R7bB0ZqjA+2C7EL7fe0o1fvzoNofMmZsbD6FK4_ZYKXdrhg@mail.gmail.com>
Date: Wed, 25 Feb 2015 16:53:24 -0800
From: Scott Feldman <sfeldma@...il.com>
To: Andy Gospodarek <gospo@...ulusnetworks.com>
Cc: Andrew Lunn <andrew@...n.ch>, "Rafa?? Mi??ecki" <zajec5@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Network Development <netdev@...r.kernel.org>,
Jonas Gorski <jogo@...nwrt.org>,
Hauke Mehrtens <hauke@...ke-m.de>,
Felix Fietkau <nbd@...nwrt.org>, Jiri Pirko <jiri@...nulli.us>
Subject: Re: [PATCH] net: phy: b53: switchdev driver for Broadcom BCM53xx switches
On Wed, Feb 25, 2015 at 7:46 AM, Andy Gospodarek
<gospo@...ulusnetworks.com> wrote:
> On Wed, Feb 25, 2015 at 03:03:56PM +0100, Andrew Lunn wrote:
> [...]
>>
>> What we don't want is X chip families and Y different ways to
>> configure the features. Ideal we want X chip families, and one way to
>> configure them all.
>
> This statement is really my primary concern. There is lots of interest
> around hardware offload at this point and it seems like there is a risk
> that a lack of consistency can create problems.
>
> I think these patches are great as they allow for the programming of the
> offload hardware (and it has been pointed out that this drastically
> increases performance), but one concern I have with this patch (related
> to this) is that I'm not sure there is a major need to create netdevs
> automatically if there is not the ability to rx/tx actual frames on
> these interfaces.
Even when not used for rx/tx to CPU, it seems the netdevs are still
useful as an anchor to build higher-level constructs such as bridge or
bond, and to hang stuff like netdev stats or ethtool-ish things.
-scott
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists