[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200309122014.22f1ed62@kicinski-fedora-PC1C0HJN>
Date: Mon, 9 Mar 2020 12:20:14 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, davem@...emloft.net, saeedm@...lanox.com,
leon@...nel.org, michael.chan@...adcom.com, vishal@...lsio.com,
jeffrey.t.kirsher@...el.com, idosch@...lanox.com,
aelior@...vell.com, peppe.cavallaro@...com,
alexandre.torgue@...com, jhs@...atatu.com,
xiyou.wangcong@...il.com, pablo@...filter.org,
ecree@...arflare.com, mlxsw@...lanox.com
Subject: Re: [patch net-next v3 09/10] flow_offload: introduce "disabled" HW
stats type and allow it in mlxsw
On Sat, 7 Mar 2020 07:56:37 +0100 Jiri Pirko wrote:
> >Would it fit better for the bitfield if disabled internally is
> >BIT(last type + 1)?
>
> I don't see why. Anyway, if needed, this can be always tweaked.
Because it makes it impossible for drivers to pass to
flow_action_hw_stats_types_check() that they support disabled.
I thought disabled means "must have no stats" but I think you may want
it to mean "no stats needed". Which probably makes more sense, right..
Powered by blists - more mailing lists