Date: Thu, 8 Sep 2011 18:28:21 +0200 From: "K. Macy" <kmacy@freebsd.org> To: Ben Hutchings <bhutchings@solarflare.com> Cc: Takuya ASADA <syuu@dokukino.com>, freebsd-net@freebsd.org, jfv@freebsd.org, John Baldwin <jhb@freebsd.org>, Navdeep Parhar <np@freebsd.org> Subject: Re: Adding Flow Director sysctls to ixgbe(4) Message-ID: <CAHM0Q_NL=vRaOJUAFsmzoODcYdscJ4CogihH2MvTTEcSNf9iPA@mail.gmail.com> In-Reply-To: <1315498877.2804.10.camel@bwh-desktop> References: <CALG4x-W99OZxd=1ZDvW4=MBqeE3RPOazc7jc_3O30X-Pou3k8Q@mail.gmail.com> <201109080834.11607.jhb@freebsd.org> <CAHM0Q_POUXeEBH2T00zDbzGh-4iuN2iML8L87_xreHr_O%2B29rg@mail.gmail.com> <201109081106.40714.jhb@freebsd.org> <1315498877.2804.10.camel@bwh-desktop>
next in thread | previous in thread | raw e-mail | index | archive | help
> Whatever the mechanism is, the interface should allow for: > > - Flexible matching on layer 2, 3 and 4 header fields > - Masking out some bits before matching (e.g. ignoring priority bits of > =A0VLAN tag or least significant bits of IPv4 address) > - Priority of rules in case several match a single flow. =A0This may > =A0need to be combined with location, since in a TCAM location may > =A0determine priority. > - Requesting packets to be dropped, steered to a single RX queue, or > =A0steered to a range of RX queues (using a flow hash and indirection > =A0table) > - Use of multiple hash indirection tables Do you feel that the Linux API for this is the right place to start looking? Earlier you said: "The exact capabilities of the hardware are all quite different and we're still recovering from the early mistake of defining two subtly different interfaces." Have the two APIs been unified, if not which one do you believe is the "right" one? Cheers
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHM0Q_NL=vRaOJUAFsmzoODcYdscJ4CogihH2MvTTEcSNf9iPA>