DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jingjing Wu <jingjing.wu@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/6] Support flow director programming on fortville
Date: Fri,  1 Aug 2014 15:08:30 +0800	[thread overview]
Message-ID: <1406876916-24869-1-git-send-email-jingjing.wu@intel.com> (raw)

The patch set supports flow director programming on fortville.
It includes:
 - reserve i40e resources for flow director, such as queue and vsi.
 - support the new ethdev AP Irx_classification_filter_ctl for all 
   the configuration or queries for receive classification filters.
 - support programming 6 flow types for the flow director filters,
   which is called PCTYPE in fortville: ipv4, tcpv4, udpv4, ipv6,
   tcpv6, udpv6.
 - support flushing flow director table (all filters).
 - support match statistics and FD ID report.
 - all fix the the Marco conflict between rte_ip.h and netinet/in.h. 

jingjing.wu (6):
  i40e: flow director resource reserve and initialize on i40e
  lib/librte_net: fix the Marco conflict between rte_ip.h and netinet/in.h
  ethdev: define new ethdev API rx_classification_filter_ctl
  i40e: function implement in i40e for flow director filter programming
  app/test-pmd: add commands and config functions for i40e flow director support
  i40e: support FD ID report and match counter for i40e flow director

 app/test-pmd/cmdline.c              | 665 ++++++++++++++++++++++++++++++++++++
 app/test-pmd/config.c               |  54 ++-
 app/test-pmd/testpmd.c              |  22 ++
 app/test-pmd/testpmd.h              |  57 ++++
 lib/librte_ether/Makefile           |   3 +-
 lib/librte_ether/rte_eth_features.h |  64 ++++
 lib/librte_ether/rte_ethdev.c       |  19 +-
 lib/librte_ether/rte_ethdev.h       | 108 +++---
 lib/librte_net/rte_ip.h             |   5 +-
 lib/librte_pmd_i40e/Makefile        |   5 +
 lib/librte_pmd_i40e/i40e_ethdev.c   |  98 +++++-
 lib/librte_pmd_i40e/i40e_ethdev.h   |  32 +-
 lib/librte_pmd_i40e/i40e_fdir.c     | 355 +++++++++++++++++++
 lib/librte_pmd_i40e/i40e_rxtx.c     | 176 +++++++++-
 lib/librte_pmd_i40e/rte_i40e.h      | 125 +++++++
 15 files changed, 1727 insertions(+), 61 deletions(-)
 create mode 100644 lib/librte_ether/rte_eth_features.h
 create mode 100644 lib/librte_pmd_i40e/i40e_fdir.c
 create mode 100644 lib/librte_pmd_i40e/rte_i40e.h

-- 
1.8.1.4

             reply	other threads:[~2014-08-01  7:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01  7:08 Jingjing Wu [this message]
2014-08-01  7:08 ` [dpdk-dev] [PATCH 1/6] i40e: flow director resource reserve and initialize on i40e Jingjing Wu
2014-08-01  7:08 ` [dpdk-dev] [PATCH 2/6] lib/librte_net: fix the Marco conflict Jingjing Wu
2014-08-01  7:08 ` [dpdk-dev] [PATCH 3/6] ethdev: define new ethdev API rx_classification_filter_ctl Jingjing Wu
2014-08-01  7:08 ` [dpdk-dev] [PATCH 4/6] i40e: function implement in i40e for flow director filter programming Jingjing Wu
2014-08-01  7:08 ` [dpdk-dev] [PATCH 5/6] app/test-pmd: add commands and config functions for i40e flow director support Jingjing Wu
2014-08-01  7:08 ` [dpdk-dev] [PATCH 6/6] i40e: support FD ID report and match counter for i40e flow director Jingjing Wu
2014-08-15  1:33 ` [dpdk-dev] [PATCH 0/6] Support flow director programming on fortville Cao, Min

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=1406876916-24869-1-git-send-email-jingjing.wu@intel.com \
    --to=jingjing.wu@intel.com \
    --cc=dev@dpdk.org \
    /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).