From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jingjing Wu <jingjing.wu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4 0/4] NIC filters support for generic filter
Date: Mon, 16 Jun 2014 20:00:41 +0200 [thread overview]
Message-ID: <2390745.NRo8ZSvNQb@xps13> (raw)
In-Reply-To: <1402903906-24307-1-git-send-email-jingjing.wu@intel.com>
2014-06-16 15:31, Jingjing Wu:
> A generic filter mechanism for handling special packet is required.
> It will allow filters to be set in HW when available so that specific
> packet may be filtered by NICs to specific descriptor queues for
> processing. Currently only Flow Director for Intel's 10GbE 82599
> devices is available. Other types of filter are not support.
> NIC filters list below are implemented in this patchset:
> ethertype filter, syn filter, 2tuple filter and flex filter for 82580 and i350
> ethertype filter, syn filter, 5tuple filter for 82576
> ethertype filter, syn filter and 5tuple filter for 82599
Reviewed-by: Vladimir Medvedkin <medvedkinv@gmail.com>
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
I've fixed some doxygen comments and logs.
Applied for version 1.7.0.
Hope to see more patches about filtering in coming weeks.
Thanks
--
Thomas
prev parent reply other threads:[~2014-06-16 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 7:31 Jingjing Wu
2014-06-16 7:31 ` [dpdk-dev] [PATCH v4 1/4] ethdev: add ethdev APIs for NIC filters of " Jingjing Wu
2014-06-16 7:31 ` [dpdk-dev] [PATCH v4 2/4] e1000: add igb NIC filters of generic filter feature Jingjing Wu
2014-06-16 7:31 ` [dpdk-dev] [PATCH v4 3/4] ixgbe: add ixgbe " Jingjing Wu
2014-06-16 7:31 ` [dpdk-dev] [PATCH v4 4/4] app/test-pmd: add commands in testpmd for NIC filters Jingjing Wu
2014-06-16 14:15 ` [dpdk-dev] [PATCH v4 0/4] NIC filters support for generic filter Cao, Waterman
2014-06-16 18:00 ` Thomas Monjalon [this message]
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=2390745.NRo8ZSvNQb@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.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).