[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55196513.8080101@cumulusnetworks.com>
Date: Mon, 30 Mar 2015 08:00:35 -0700
From: roopa <roopa@...ulusnetworks.com>
To: Andy Gospodarek <gospo@...ulusnetworks.com>
CC: Jiri Pirko <jiri@...nulli.us>, sfeldma@...il.com,
netdev@...r.kernel.org, linux@...ck-us.net, f.fainelli@...il.com
Subject: Re: [PATCH net-next 00/18] switchdev: spring cleanup
On 3/30/15, 6:11 AM, Andy Gospodarek wrote:
> On Mon, Mar 30, 2015 at 02:00:25PM +0200, Jiri Pirko wrote:
>> Mon, Mar 30, 2015 at 10:40:18AM CEST, sfeldma@...il.com wrote:
>>> From: Scott Feldman <sfeldma@...il.com>
>>>
>>> The main theme of this patch set is to cleanup swdev in preparation for
>>> new features or fixes to be added soon. We have a pretty good idea now how
>>> to handle stacked drivers in swdev, but there where some loose ends. For
>>> example, if a set failed in the middle of walking the lower devs, we would
>>> leave the system in an undefined state...there was no way to recover back to
>>> the previous state. Speaking of sets, also recognize a pattern that most
>>> swdev API accesses are gets or sets of port attributes, so go ahead and make
>>> port attr get/set the central swdev API, and convert everything that is
>>> set-ish/get-ish to this new API.
>>>
>>> Features/fixes that should follow from this cleanup:
>>>
>>> - solve the duplicate pkt forwarding issue
>>> - get/set bridge attrs, like ageing_time, from/to device
>>> - get/set more bridge port attrs from/to device
>>>
>>> There are some rename cleanups tagging along at the end, to give swdev
>>> consistent naming.
>> As you can see in the switchdev patch submission history, I originally
>> pushed this with "swdev_" previx. Turned out people did not like that
>> because "sw" can be easily misunderstood as "software".
> I agree with this.
>
agree. maybe just "switchdev_" will be better.
--
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