netdev - Re: Interface proposal for rx classification using ethtool

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] [thread-next>] [day] [month] [year] [list]

Message-id: <48F8D673.5070101@Sun.COM>
Date:	Fri, 17 Oct 2008 11:16:19 -0700
From:	Santwona.Behera@....COM
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, gkernel-commit@...ts.sourceforge.net,
	Matheos Worku <Matheos.Worku@....COM>
Subject: Re: Interface proposal for rx classification using ethtool



On 10/15/08 16:19, David Miller wrote:
> From: Santwona.Behera@....COM
> Date: Mon, 29 Sep 2008 10:28:07 -0700
> 
>> Here is the proposed design for implementing an interface to add, delete and
>> manage rules for RX packet classification on ethertool with niu as the first
>> target hardware. This is the second installment of network flow classification
>> support (the first one was for rx flow distribution based on hashing that was
>> added in June). Please review and send your feedback.
> 
> This looks mostly fine to me, thanks for working on this.
> 
> I do have one question though.
> 
> At least to some extent the user will have to have a way to
> figure out that multiple interfaces correspond to one instance
> of the TCAM.  Because this determines sharing and other
> aspects, right?

That will not be the case as the driver will partition the TCAM on a per
interface basis. So the entries for each interface will be independent
of each other. This has been done to make the ethtool interface
independent of the TCAM implementation, i.e., if there are multiple
TCAMs in any future revs of the hardware or in any other hardware, the
per port API should work.

> 
> How it seems to work in your description is that the user operates on
> (for example) eth0 and eth1 as if they were independant objects, but
> if the TCAM fills up that will be seen equally by operations on both
> interfaces.

Each partition in the TCAM will fill up independently for each
interface.

> 
> But, to be honest this is a minor detail.
> 
> They may also be value in allowing TCAM entries to be locked by the
> kernel and thus be unmodifyable by the user.

That will be the case. All updates will be done by the driver to
implement the partitioning.

> 
> For example, in NIU, those special workaround entries we add to handle
> IP fragments would be a candidate for this.

That is right. In fact these entries will be put in by the driver and
will not be exported to the user. The partitioning for each port will
start in the region after these entries.

--santwona
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html