From: "Zhang, Helin" <helin.zhang@intel.com>
To: Kamraan Nasim <knasim@sidebandnetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Ean Houts <ehouts@sidebandnetworks.com>,
Jun Du <jdu@sidebandnetworks.com>
Subject: Re: [dpdk-dev] Does I210 NIC support Flow director filters?
Date: Wed, 14 Jan 2015 07:42:24 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7E85BF@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAPrTskjo7U_eGpprgLyJ0WDYy6eSttwRswobUP3mxNpsfLy0qw@mail.gmail.com>
FD should works on all supported NICs, though might not all FD features have been implemented. You can see some reworks are ongoing from the mail list.
Regards,
Helin
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kamraan Nasim
> Sent: Wednesday, January 14, 2015 12:21 PM
> To: dev@dpdk.org
> Cc: Ean Houts; Jun Du
> Subject: [dpdk-dev] Does I210 NIC support Flow director filters?
>
> Hello,
>
> I've been using DPDK fdir filter APIs for 82599 NIC(Niantic) and they work very
> well.
>
> Was wondering if I these could also be used for I210, 1Gbps NICs?
>
> The other option is to use 5tuple filters(rte_eth_dev_add_5tuple_filter
> <http://dpdk.org/doc/api/rte__ethdev_8h.html#aaa28adafa65a4f47d4aeceaf1
> b08381b>),
> however these do not support IPv6 yet.
>
>
> Have people in the community had any luck with configuring L3/L4 hardware
> filters for the I210 NIC?
>
> Thanks,
> Kam
next prev parent reply other threads:[~2015-01-14 7:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 4:21 Kamraan Nasim
2015-01-14 7:42 ` Zhang, Helin [this message]
2015-01-14 10:27 ` Bruce Richardson
2015-01-14 21:59 ` Kamraan Nasim
2015-01-15 14:44 ` Bruce Richardson
2015-01-16 1:06 ` Kamraan Nasim
2015-01-16 10:56 ` Bruce Richardson
2015-01-16 16:42 ` Kamraan Nasim
2015-01-16 17:31 ` Bruce Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F35DEAC7BCE34641BA9FAC6BCA4A12E70A7E85BF@SHSMSX104.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=ehouts@sidebandnetworks.com \
--cc=jdu@sidebandnetworks.com \
--cc=knasim@sidebandnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).