DPDK patches and discussions
 help / color / mirror / Atom feed
From: Mesut Ali Ergin <mesut.a.ergin@intel.com>
To: beilei.xing@intel.com, qi.z.zhang@intel.com
Cc: dev@dpdk.org, Mesut Ali Ergin <mesut.a.ergin@intel.com>
Subject: [dpdk-dev] [PATCH 3/3] net/i40e: fix inadvertent override of vector RX allowance
Date: Wed, 15 May 2019 21:28:05 -0700	[thread overview]
Message-ID: <1557980885-183777-4-git-send-email-mesut.a.ergin@intel.com> (raw)
In-Reply-To: <1557980885-183777-1-git-send-email-mesut.a.ergin@intel.com>

When i40e_rx_vec_dev_conf_condition_check_default() determines whether
vector receive functions would be allowed during initialization phase,
it should honor previously recorded disallowance during configuration
phase, and not override simply because it is for the first queue.

Signed-off-by: Mesut Ali Ergin <mesut.a.ergin@intel.com>
---
 drivers/net/i40e/i40e_rxtx_vec_common.h | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/net/i40e/i40e_rxtx_vec_common.h b/drivers/net/i40e/i40e_rxtx_vec_common.h
index 0e6ffa0..f30cab4 100644
--- a/drivers/net/i40e/i40e_rxtx_vec_common.h
+++ b/drivers/net/i40e/i40e_rxtx_vec_common.h
@@ -212,6 +212,10 @@ i40e_rx_vec_dev_conf_condition_check_default(struct rte_eth_dev *dev)
 	if (rxmode->offloads & DEV_RX_OFFLOAD_VLAN_EXTEND)
 		return -1;
 
+	/* Should not override if vector was already disallowed */
+	if (!ad->rx_vec_allowed)
+	return -1;
+
 	/**
 	 * Vector mode is allowed only when number of Rx queue
 	 * descriptor is power of 2.
-- 
2.7.4

  parent reply	other threads:[~2019-05-16  4:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  4:28 [dpdk-dev] [PATCH 0/3] net/i40e: improve rte_flow offload with MARK + RSS Mesut Ali Ergin
2019-05-16  4:28 ` Mesut Ali Ergin
2019-05-16  4:28 ` [dpdk-dev] [PATCH 1/3] net/i40e: add support for MARK + RSS action in rte_flow Mesut Ali Ergin
2019-05-16  4:28   ` Mesut Ali Ergin
2019-05-22 12:30   ` Zhang, Qi Z
2019-05-16  4:28 ` [dpdk-dev] [PATCH 2/3] net/i40e: add runtime option to disable vector rx Mesut Ali Ergin
2019-05-16  4:28   ` Mesut Ali Ergin
2019-05-16  8:17   ` Maxime Coquelin
2019-05-16  8:17     ` Maxime Coquelin
2019-05-16 21:26     ` Ergin, Mesut A
2019-05-20  8:29   ` Ananyev, Konstantin
2019-05-20 17:53     ` Ergin, Mesut A
2019-05-20 23:11       ` Ananyev, Konstantin
2019-05-21 16:33         ` Ergin, Mesut A
2019-05-21 17:20           ` Ananyev, Konstantin
2019-05-21 20:55             ` Ergin, Mesut A
2019-05-22 11:01               ` Ananyev, Konstantin
2019-05-22 14:05                 ` Thomas Monjalon
2019-05-22 14:32                   ` Zhang, Qi Z
2019-05-23 13:10                     ` Jerin Jacob Kollanukkaran
2019-05-23 17:54                 ` Ergin, Mesut A
2019-05-16  4:28 ` Mesut Ali Ergin [this message]
2019-05-16  4:28   ` [dpdk-dev] [PATCH 3/3] net/i40e: fix inadvertent override of vector RX allowance Mesut Ali Ergin
2019-05-16  8:17   ` Maxime Coquelin
2019-05-16  8:17     ` Maxime Coquelin
2019-05-16 20:57     ` Ergin, Mesut A
2019-05-22 12:42   ` Zhang, Qi Z
2019-05-23 18:25     ` Ergin, Mesut A
2019-05-24  2:39       ` Zhang, Qi Z
2019-05-24 18:08         ` Ergin, Mesut A
2019-05-25 11:29           ` Zhang, Qi Z

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=1557980885-183777-4-git-send-email-mesut.a.ergin@intel.com \
    --to=mesut.a.ergin@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@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).