From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Sujith Sankar (ssujith)" <ssujith@cisco.com>
Cc: dev@dpdk.org, "Prasad Rao \(prrao\)" <prrao@cisco.com>
Subject: Re: [dpdk-dev] [PATCH v6 5/6] enicpmd: DPDK-ENIC PMD interface
Date: Tue, 06 Jan 2015 10:41:54 +0100 [thread overview]
Message-ID: <2166065.bfoVCtWc4v@xps13> (raw)
In-Reply-To: <D0C82A9E.2BA5D%ssujith@cisco.com>
2014-12-30 04:45, Sujith Sankar:
> On 29/12/14 1:45 pm, "Wu, Jingjing" <jingjing.wu@intel.com> wrote:
> >I found that in perfect fdir is also supported in enic driver.
> >
> >During the R1.8 development, we defined a new dev_ops call filter_ctrl,
> >which can be used to control kinds of filters, flow director is included
> >too. Which is mentioned in
> >http://www.dpdk.org/ml/archives/dev/2014-September/005179.html .
> >In R1.8, filter_ctrl is only used by i40e driver. And we also planned use
> >it in the existing ixgbe/e1000 driver in the next days. The old APIs such
> >as fdir_add_perfect_filter, fdir_remove_perfect_filter can be replaced
> >then.
>
> Hi Jingjing,
> Thanks for the info and the link. I shall take a look at it.
> It looks like bringing in one interface for all filter related operations.
> I believe ENIC should also move to it.
Yes please.
It is planned to remove or deprecate old flow director API.
--
Thomas
next prev parent reply other threads:[~2015-01-06 9:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 17:26 [dpdk-dev] [PATCH v6 0/6] enicpmd: Cisco Systems Inc. VIC Ethernet PMD Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 1/6] enicpmd: License text Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 2/6] enicpmd: Makefile Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 3/6] enicpmd: VNIC common code partially shared with ENIC kernel mode driver Sujith Sankar
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 4/6] enicpmd: pmd specific code Sujith Sankar
2014-11-27 14:49 ` Wodkowski, PawelX
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 5/6] enicpmd: DPDK-ENIC PMD interface Sujith Sankar
2014-12-29 8:15 ` Wu, Jingjing
2014-12-30 4:45 ` Sujith Sankar (ssujith)
2015-01-06 9:41 ` Thomas Monjalon [this message]
2015-01-30 8:53 ` Wu, Jingjing
2014-11-25 17:26 ` [dpdk-dev] [PATCH v6 6/6] enicpmd: DPDK changes for accommodating ENIC PMD Sujith Sankar
2014-11-25 19:51 ` [dpdk-dev] [PATCH v6 0/6] enicpmd: Cisco Systems Inc. VIC Ethernet PMD David Marchand
2014-11-26 22:11 ` Thomas Monjalon
2014-11-27 4:27 ` Sujith Sankar (ssujith)
2014-11-27 15:31 ` Thomas Monjalon
2015-01-20 11:25 ` David Marchand
2015-01-21 5:03 ` Sujith Sankar (ssujith)
2015-02-26 11:49 ` Thomas Monjalon
2015-02-26 13:08 ` Wiles, Keith
2015-02-27 8:09 ` Sujith Sankar (ssujith)
2015-02-27 8:47 ` [dpdk-dev] Why only rx queue "0" can receive network packet by i40e NIC lhffjzh
2015-02-27 9:03 ` lhffjzh
2015-02-27 10:55 ` Thomas Monjalon
2015-02-28 1:47 ` lhffjzh
2015-02-28 3:17 ` Zhang, Helin
2015-02-28 4:33 ` lhffjzh
2015-02-28 14:33 ` Zhang, Helin
2015-07-23 0:47 ` Jeff Venable, Sr.
2015-07-23 0:56 ` Zhang, Helin
2015-07-30 1:58 ` Jeff Venable, Sr.
2015-07-31 15:35 ` Zhang, Helin
2015-02-27 10:46 ` [dpdk-dev] [PATCH v6 0/6] enicpmd: Cisco Systems Inc. VIC Ethernet PMD Thomas Monjalon
2015-03-11 9:05 ` Sujith Sankar (ssujith)
2015-05-11 9:25 ` Thomas Monjalon
2014-11-25 20:11 ` Neil Horman
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=2166065.bfoVCtWc4v@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=prrao@cisco.com \
--cc=ssujith@cisco.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).