| commit | 434495c50ea786b89eca7f7af2bac424658a76ee | |
| author | Ben Hutchings <bhutchings@solarflare.com> | |
| Tue, 6 Sep 2011 13:48:56 +0000 (6 13:48 +0000) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Fri, 16 Sep 2011 23:25:10 +0000 (16 19:25 -0400) | ||
| tree | b3d0d8473f76f7b85aa8822c1df92e336cbe0f37 | treesnapshot (tar.gz zip) |
| parent | 9927c893f4442f5045a919ff7c78113ded9c709e | commitdiff |
ethtool: Explicitly state that RX NFC rule locations are priorities
The location of an RX flow classification rule is needed to identify
it for retrieval, replacement or deletion. However it also defines
the priority of the rule in the case that a flow is matched by
multiple rules. This is what I intended to imply by referring to the
use of a TCAM, commonly used to implement that behaviour.
However there are other ways this can be done, and it is better to
specify this explicitly. Further, I want to add the option for
automatic selection of rule locations.
Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
The location of an RX flow classification rule is needed to identify
it for retrieval, replacement or deletion. However it also defines
the priority of the rule in the case that a flow is matched by
multiple rules. This is what I intended to imply by referring to the
use of a TCAM, commonly used to implement that behaviour.
However there are other ways this can be done, and it is better to
specify this explicitly. Further, I want to add the option for
automatic selection of rule locations.
Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
| include/linux/ethtool.h | diffblobblamehistory |