[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170208.135415.601520734521006340.davem@davemloft.net>
Date: Wed, 08 Feb 2017 13:54:15 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: tom@...bertland.com
Cc: simon.horman@...ronome.com, jiri@...nulli.us,
eric.dumazet@...il.com, dinan.gunawardena@...ronome.com,
netdev@...r.kernel.org, oss-drivers@...ronome.com
Subject: Re: [oss-drivers] Re: [PATCH/RFC net-next 1/2] flow dissector: ND
support
From: Tom Herbert <tom@...bertland.com>
Date: Wed, 8 Feb 2017 10:33:46 -0800
> On Wed, Feb 8, 2017 at 1:28 AM, Simon Horman <simon.horman@...ronome.com> wrote:
>> I think the above paragraph gets back to Tom's original question regarding
>> making things more complex just for OvS (use-cases). Possibly ND is an edge
>> case even for OvS and on reflection my timing for posting it seems to have
>> been less than ideal.
>
> If it wasn't ND it would be something else... with all the activity
> happening in networking features and HW this is a timely discussion.
> Flow dissector presents a good example of a function that might become
> a dumping ground for an endless stream of features if we don't figure
> out how exercise some restraint.
I agree on most points.
But, I would say that in this specific case, since we have ARP support in
there already it behooves us to support the ipv6 side in the form of ND
too.
Then we can put a line in the sand and say that future feature additions
in this area require serious discussion.
Ok Tom?
Powered by blists - more mailing lists