[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1718a74b-3684-0160-466f-04495be5f0ca@solarflare.com>
Date: Thu, 23 May 2019 17:40:08 +0100
From: Edward Cree <ecree@...arflare.com>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>,
Jamal Hadi Salim <jhs@...atatu.com>
CC: Jiri Pirko <jiri@...nulli.us>,
Pablo Neira Ayuso <pablo@...filter.org>,
David Miller <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
"Cong Wang" <xiyou.wangcong@...il.com>,
Andy Gospodarek <andy@...yhouse.net>,
Michael Chan <michael.chan@...adcom.com>,
Vishal Kulkarni <vishal@...lsio.com>
Subject: Re: [PATCH v3 net-next 0/3] flow_offload: Re-add per-action
statistics
On 23/05/2019 17:11, Jakub Kicinski wrote:
> On Thu, 23 May 2019 09:19:49 -0400, Jamal Hadi Salim wrote:
>> That would still work here, no? There will be some latency
>> based on the frequency of hardware->kernel stats updates.
> I don't think so, I think the stats are only updated on classifier
> dumps in Ed's code.
Yep currently that's the case, but not as an inherent restriction (see
my other mail).
> But we can't be 100% sure without seeing driver code.
Would it help if I posted my driver code to the list? It's gonna be
upstream eventually anyway, it's just that the driver as a whole
isn't really in a shape to be merged just yet (mainly 'cos the
hardware folks are planning some breaking changes). But I can post
my TC handling code, or even the whole driver, if demonstrating how
these interfaces can be used will help matters.
-Ed
Powered by blists - more mailing lists