[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cd59f9e3-1bc3-0e2b-3c77-52373567bb73@mojatatu.com>
Date: Fri, 7 Aug 2020 06:41:29 -0400
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Ariel Levkovich <lariel@...lanox.com>, netdev@...r.kernel.org,
kuba@...nel.org, xiyou.wangcong@...il.com, ast@...nel.org,
daniel@...earbox.net
Subject: Re: [PATCH net-next v2 0/3] ] TC datapath hash api
On 2020-07-10 8:04 a.m., Jamal Hadi Salim wrote:
> On 2020-07-09 8:19 a.m., Jiri Pirko wrote:
>> Thu, Jul 09, 2020 at 01:00:26PM CEST, jhs@...atatu.com wrote:
>>>
>>> Main point is: classifying based on hash(and for that
>>> matter any other metadata like mark) is needed as a general
>>> utility for the system and should not be only available for
>>> flower. The one big reason we allow all kinds of classifiers
>>> in tc is in the name of "do one thing and do it well".
>>
>> Sure. That classifier can exist, no problem. At the same time, flower
>> can match on it as well. There are already multiple examples of
>> classifiers matching on the same thing. I don't see any problem there.
>>
>
> I keep pointing to the issues and we keep circling back
> to your desire to add it to flower. I emphatize with the
> desire to have flower as a one stop shop for all things classification
> but this is at the expense of other classifiers. I too need this for
> offloading as well as getting the RSS proper feature i described.ets
> make progress.
> You go ahead - i will submit a version to add it as a separate
> hash classifier.
>
Some cycles opened up - I will work on this in the next day or
two now that your patches are in...
cheers,
jamal
Powered by blists - more mailing lists