lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 11 Feb 2019 11:44:35 +0000
From:   Edward Cree <>
To:     Jamal Hadi Salim <>,
        netdev <>
CC:     Jiri Pirko <>,
        Cong Wang <>,
        "Or Gerlitz" <>,
        Andy Gospodarek <>,
        "PJ Waskiewicz" <>,
        Anjali Singhai Jain <>,
        Jakub Kicinski <>
Subject: Re: TC stats / hw offload question

On 09/02/19 17:39, Jamal Hadi Salim wrote:
> On 2019-02-08 5:26 a.m., Edward Cree wrote:
>>   I can't find any stats counters on
>>   the "match" either in the software path or the offload API.
> Hasnt been necessary thus far.
> Is your end goal to match and count?
My end goal is to implement TC offload in some hw we're designing
 here at Solarflare.  So I'm trying to determine what hardware is
 expected/required to do.
It might be possible to design our new hw so that we can attach a
 counter to every action, if that's what TC wants.  But since the
 other vendors don't seem to do that, I wondered if there was a
 reason, or if perhaps the counter resources (and PCI bw to read
 them) could be saved if all those separate counters aren't really
 needed.  Right now the design we are considering would only count
 packets as-matched, i.e. before any edits.  That's fine for encap
 — you can calculate the bytes correction in SW — but not for decap
 since in principle the length of the RXed outer headers could
 vary (e.g. you might have IP options there).


Powered by blists - more mailing lists