DPDK patches and discussions
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/5] Assorted fixes for the flow API
Date: Tue, 10 Jan 2017 14:08:25 +0100	[thread overview]
Message-ID: <cover.1484046037.git.adrien.mazarguil@6wind.com> (raw)

This series makes a few adjustments to the flow API (rte_flow) based on
issues encountered by preliminary PMD implementations and addresses bugs
reported by Coverity in the testpmd flow command.

Adrien Mazarguil (5):
  app/testpmd: fix array bounds checks
  ethdev: modify flow API's error setting function
  ethdev: clarify MARK and FLAG actions in flow API
  ethdev: clarify RSS action in flow API
  ethdev: define default item masks in flow API

 app/test-pmd/config.c              |   8 +-
 app/test-pmd/rxonly.c              |   3 +-
 doc/guides/prog_guide/rte_flow.rst |  57 +++++++------
 lib/librte_ether/rte_flow.c        |  24 +++---
 lib/librte_ether/rte_flow.h        | 137 +++++++++++++++++++++++++++-----
 lib/librte_ether/rte_flow_driver.h |   6 +-
 6 files changed, 170 insertions(+), 65 deletions(-)

-- 
2.1.4

             reply	other threads:[~2017-01-10 13:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 13:08 Adrien Mazarguil [this message]
2017-01-10 13:08 ` [dpdk-dev] [PATCH 1/5] app/testpmd: fix array bounds checks Adrien Mazarguil
2017-01-10 13:08 ` [dpdk-dev] [PATCH 2/5] ethdev: modify flow API's error setting function Adrien Mazarguil
2017-01-10 13:08 ` [dpdk-dev] [PATCH 3/5] ethdev: clarify MARK and FLAG actions in flow API Adrien Mazarguil
2017-01-10 13:08 ` [dpdk-dev] [PATCH 4/5] ethdev: clarify RSS action " Adrien Mazarguil
2017-01-10 13:08 ` [dpdk-dev] [PATCH 5/5] ethdev: define default item masks " Adrien Mazarguil
2017-01-11 15:57 ` [dpdk-dev] [PATCH 0/5] Assorted fixes for the " Thomas Monjalon

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=cover.1484046037.git.adrien.mazarguil@6wind.com \
    --to=adrien.mazarguil@6wind.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).