DPDK patches and discussions
 help / color / mirror / Atom feed
From: rory.sexton@intel.com
To: jingjing.wu@intel.com
Cc: dev@dpdk.org, Rory Sexton <rory.sexton@intel.com>,
	Nemanja Marjanovic <nemanja.marjanovic@intel.com>
Subject: [dpdk-dev] [PATCH v2] net/i40e: set no drop for traffic class
Date: Mon, 16 Jan 2017 15:52:28 +0000	[thread overview]
Message-ID: <1484581948-10736-1-git-send-email-rory.sexton@intel.com> (raw)
In-Reply-To: <9BB6961774997848B5B42BEC655768F810CBEF56@SHSMSX103.ccr.corp.intel.com>

From: Rory Sexton <rory.sexton@intel.com>

The default traffic class in i40e is set to drop versus on ixgbe
it isset to no drop. This means when packets build up in the RX
SRAM on the NIC, they are dropped, and they do this when the SW
descriptor rings fill up.

This patch changes this behaviour and our testing shows there
are no drops as a result.

Signed-off-by: Rory Sexton <rory.sexton@intel.com>
Signed-off-by: Nemanja Marjanovic <nemanja.marjanovic@intel.com>
---
v2:
* Changed to use existing api to set priority register directly.

 drivers/net/i40e/i40e_ethdev.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/net/i40e/i40e_ethdev.c b/drivers/net/i40e/i40e_ethdev.c
index 67778ba..97339b5 100644
--- a/drivers/net/i40e/i40e_ethdev.c
+++ b/drivers/net/i40e/i40e_ethdev.c
@@ -2985,8 +2985,11 @@ static int
 i40e_priority_flow_ctrl_set(__rte_unused struct rte_eth_dev *dev,
 			    __rte_unused struct rte_eth_pfc_conf *pfc_conf)
 {
+	struct i40e_hw *hw = I40E_DEV_PRIVATE_TO_HW(dev->data->dev_private);
+
 	PMD_INIT_FUNC_TRACE();
 
+	I40E_WRITE_REG(hw, I40E_PRTDCB_TC2PFC, 0xff);
 	return -ENOSYS;
 }
 
-- 
2.4.3

  reply	other threads:[~2017-01-16 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-04 13:54 [dpdk-dev] [PATCH v1] " Rory Sexton
2016-12-05  8:44 ` Wu, Jingjing
2016-12-09 14:02   ` Sexton, Rory
2016-12-26  8:45     ` Wu, Jingjing
2017-01-16 15:52       ` rory.sexton [this message]
2017-01-17 15:09         ` [dpdk-dev] [PATCH v2] " Wu, Jingjing
2017-01-19 10:38           ` Sexton, Rory
2017-02-07 15:25             ` Wu, Jingjing
2017-02-09 15:34               ` Ferruh Yigit

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=1484581948-10736-1-git-send-email-rory.sexton@intel.com \
    --to=rory.sexton@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=nemanja.marjanovic@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).