DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahed Shaikh <shshaikh@marvell.com>
To: <dev@dpdk.org>
Cc: <rmody@marvell.com>, <jerinj@marvell.com>,
	<GR-Everest-DPDK-Dev@marvell.com>
Subject: [dpdk-dev] [PATCH v1 0/5] net/qede: fixes and enhancement
Date: Fri, 6 Sep 2019 00:32:12 -0700	[thread overview]
Message-ID: <20190906073217.13873-1-shshaikh@marvell.com> (raw)

First four patches are part of a fix for the ovs-dpdk issue
with 100Gb NIC [1].
Fifth patch adds support for drop action in rte_flow.

[1]
As per HW design of 100Gb mode, device internally uses 2 engines
(eng0 and eng1), and both engines need to be configured symmetrically.
Based on this requirement, driver design chose an approach
to allow user to allocate only even number of queues and split
those queues on both engines equally.

This approach puts a limitation on number of queues to be allocated -
i.e. user can't configure odd number of queues on 100Gb mode.
OVS configures DPDK port with 1 rxq and 1 txq, which causes initialization
of qede port to fail.

This patch series changes the implementation of queue allocation method
for 100Gb devices by removing above mentioned limitation and allowing
user to configure odd number of queues.

Fix is split into 4 logical patches -
 - First patch refactors Rx and Tx queue setup code to lay a foundation
   for actual fix.
 - Second patch actually implements a new approach to fix the issue.
 - Third patch fixes RSS configuration w.r.t. new approach.
 - Fourth patch fixes statistics code impacted due to new approach.

Shahed Shaikh (5):
  net/qede: refactor Rx and Tx queue setup
  net/qede: fix ovs-dpdk failure when using odd number of queues on
    100Gb mode
  net/qede: fix RSS configuration as per new 100Gb queue allocation
    method
  net/qede: fix stats flow as per new 100Gb queue allocation method
  net/qede: implement rte_flow drop action

 doc/guides/nics/qede.rst              |  39 +++
 drivers/net/qede/base/ecore_dev_api.h |   1 +
 drivers/net/qede/base/ecore_l2.c      |  50 ++--
 drivers/net/qede/base/ecore_l2_api.h  |  39 ++-
 drivers/net/qede/qede_ethdev.c        | 331 +++++++++++------------
 drivers/net/qede/qede_ethdev.h        |   6 +-
 drivers/net/qede/qede_filter.c        |  27 +-
 drivers/net/qede/qede_rxtx.c          | 362 +++++++++++++++++++-------
 drivers/net/qede/qede_rxtx.h          |  26 +-
 9 files changed, 549 insertions(+), 332 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-09-06  7:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06  7:32 Shahed Shaikh [this message]
2019-09-06  7:32 ` [dpdk-dev] [PATCH v1 1/5] net/qede: refactor Rx and Tx queue setup Shahed Shaikh
2019-09-12 12:34   ` Jerin Jacob
2019-09-12 14:48     ` Shahed Shaikh
2019-09-06  7:32 ` [dpdk-dev] [PATCH v1 2/5] net/qede: fix ovs-dpdk failure when using odd number of queues on 100Gb mode Shahed Shaikh
2019-09-06  7:32 ` [dpdk-dev] [PATCH v1 3/5] net/qede: fix RSS configuration as per new 100Gb queue allocation method Shahed Shaikh
2019-09-06  7:32 ` [dpdk-dev] [PATCH v1 4/5] net/qede: fix stats flow " Shahed Shaikh
2019-09-06  7:32 ` [dpdk-dev] [PATCH v1 5/5] net/qede: implement rte_flow drop action Shahed Shaikh

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=20190906073217.13873-1-shshaikh@marvell.com \
    --to=shshaikh@marvell.com \
    --cc=GR-Everest-DPDK-Dev@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=rmody@marvell.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).