[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081215.225013.248487837.davem@davemloft.net>
Date: Mon, 15 Dec 2008 22:50:13 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: peter.p.waskiewicz.jr@...el.com
Cc: netdev@...r.kernel.org, Santwona.Behera@....COM,
Matheos.Worku@....COM
Subject: Re: net: RFC ethtool 5-tuple filter set/get feature
From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
Date: Mon, 15 Dec 2008 18:52:07 -0800 (Pacific Standard Time)
> I am looking at current methods to support adding 5-tuple filters to a
> network device. 3 methods I can see are 1) Creating a sysfs interface, 2)
> writing a custom application using netlink or some other interface, or 3)
> Adding support to ethtool.
I'm pretty sure ethtool is the best mechanism currently.
> The latest ethtool bits support the rxhash callbacks, allowing different
> Rx hashing methods to be enabled or disabled in Sun's Neptune device. I
> would like to add similar options to ethtool to support features in
> current versions of igb hardware, and in future ixgbe hardware.
You could extend the existing RXHASH ethtool thing, adding your
key specifiers and some capability flags.
Actually, the Neptune folks (Santwona and Matheos CC:'d) are working
on ethtool interfaces to load TCAM entries, which would specify the
same things (except be a lot more flexible, multiple entries can be
loaded into Neptune, up to 128 or 256, with all kinds of masking etc.)
We could represent igb/ixgbe as a TCAM with one entry and no
masking support. Or something like that.
You can find their proposal by looking for "Interface proposal for rx
classification using ethtool" subject in the netdev archives for
September 2008. I believe it was posted on the 29th.
--
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
Powered by blists - more mailing lists