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: <20081015.161915.153810861.davem@davemloft.net>
Date:	Wed, 15 Oct 2008 16:19:15 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	Santwona.Behera@....COM
Cc:	netdev@...r.kernel.org, gkernel-commit@...ts.sourceforge.net,
	Matheos.Worku@....COM
Subject: Re: Interface proposal for rx classification using ethtool

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?

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.

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.

For example, in NIU, those special workaround entries we add to handle
IP fragments would be a candidate for this.
--
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