[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMh=zOZX0yQEoi0T_zC+je2_ux=mSW0qG_sSr+2eyA_81A@mail.gmail.com>
Date: Sun, 12 Feb 2017 11:54:25 +0200
From: Or Gerlitz <gerlitz.or@...il.com>
To: David Miller <davem@...emloft.net>
Cc: Or Gerlitz <ogerlitz@...lanox.com>,
Daniel Borkmann <daniel@...earbox.net>,
Jakub Kicinski <jakub.kicinski@...ronome.com>,
John Fastabend <john.r.fastabend@...el.com>,
Amir Vadai <amir@...ai.me>,
Linux Netdev List <netdev@...r.kernel.org>,
Jiri Pirko <jiri@...lanox.com>,
Paul Blakey <paulb@...lanox.com>, Roi Dayan <roid@...lanox.com>
Subject: Re: [PATCH net-next 0/4] net/sched: Use TC skip flags to reflect HW
offload status
On Fri, Feb 10, 2017 at 9:36 PM, David Miller <davem@...emloft.net> wrote:
> From: Or Gerlitz <ogerlitz@...lanox.com>
> Date: Thu, 9 Feb 2017 16:18:04 +0200
>
>> Currently there is no way of querying whether a filter is
>> offloaded to HW or not when using both policy (no flag).
>>
>> Reuse the skip flags to show the insertion status by setting
>> the skip_hw flag in case the filter wasn't offloaded.
>>
>> The bpf patch is compile tested only, Daniel/Jakub, will
>> appreciate your review/ack.
> ...
>
> I'm learning towards suggesting that you use new flags, this way it
> will be unambiguous whether we are running an old kernel.
> If you just use the skip flag, it's impossible to tell the difference.
Dave,
Re the old kernel argument, these patches are small and pointish,
would it make sense
to you to consider them as fixes and push them back to the relevant
stable kernels?
Or.
Powered by blists - more mailing lists