netdev - Re: [PATCH net-next v2 3/5] cxgb4: add parser to translate u32 filters to internal spec

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20160917084018.GA6429@chelsio.com>
Date:   Sat, 17 Sep 2016 14:10:19 +0530
From:   Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>
To:     John Fastabend <john.fastabend@...il.com>
Cc:     netdev@...r.kernel.org, davem@...emloft.net,
        hariprasad@...lsio.com, leedom@...lsio.com, nirranjan@...lsio.com,
        indranil@...lsio.com
Subject: Re: [PATCH net-next v2 3/5] cxgb4: add parser to translate u32
 filters to internal spec

On Thursday, September 09/15/16, 2016 at 07:27:24 -0700, John Fastabend wrote:
> On 16-09-13 04:42 AM, Rahul Lakkireddy wrote:
> > Parse information sent by u32 into internal filter specification.
> > Add support for parsing several fields in IPv4, IPv6, TCP, and UDP.
> > 
> > Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>
> > Signed-off-by: Hariprasad Shenai <hariprasad@...lsio.com>
> > ---
> 
> Looks good to me. Also curious if you would find it worthwhile to
> have a cls_u32 mode that starts at L2 instead of the IP header? The
> use case would be to use cls_u32 with various encapsulation protocols
> in front of the IP header.
> 
> Reviewed-by: John Fastabend <john.r.fastabend@...el.com>

Thanks for the review John.  Yes, we are also looking for getting u32
to start from L2 header in order to allow matching encapsulation
protocols in front of IP header.

In addition, our hardware also keeps track of per-filter statistics
such as number of times the filter has been hit and number of bytes
that hit the filter. Hence, we are also looking for exposing these
per-filter stats to u32.

Thanks,
Rahul