DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/ixgbe: fix hierarchy commit check
Date: Wed, 26 Jul 2017 15:20:29 +0000	[thread overview]
Message-ID: <7C6EB08A-CFB3-4631-9B02-3892E209E5C3@intel.com> (raw)
In-Reply-To: <1501080853-88038-1-git-send-email-wenzhuo.lu@intel.com>


> On Jul 26, 2017, at 9:54 AM, Wenzhuo Lu <wenzhuo.lu@intel.com> wrote:
> 
> If there's no Traffic Management node added,
> not necessary to check if TM is committed.
> 
> Fixes: 5713ade69776 ("net/ixgbe: support committing TM hierarchy")
> 
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
> ---
> drivers/net/ixgbe/ixgbe_ethdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ixgbe/ixgbe_ethdev.c b/drivers/net/ixgbe/ixgbe_ethdev.c
> index 194058f..e436dca 100644
> --- a/drivers/net/ixgbe/ixgbe_ethdev.c
> +++ b/drivers/net/ixgbe/ixgbe_ethdev.c
> @@ -2693,7 +2693,7 @@ static int eth_ixgbevf_pci_remove(struct rte_pci_device *pci_dev)
> 	ixgbe_l2_tunnel_conf(dev);
> 	ixgbe_filter_restore(dev);
> 
> -	if (!tm_conf->committed)
> +	if (tm_conf->root && !tm_conf->committed)
> 		PMD_DRV_LOG(WARNING,
> 			    "please call hierarchy_commit() "
> 			    "before starting the port”);

This patch may work on ixgbe, but I am using i40e and the message is still present. I tried to apply your logic above and that seemed to fix the i40e message.

Looks like you need to change all of the drivers that use this logic.

Here is the i40e change:

i40e_dev_start()
-    if (!pf->tm_conf.committed)
+    if (pf->tm_conf.root && !pf->tm_conf.committed)

> -- 
> 1.9.3
> 

Regards,
Keith


  parent reply	other threads:[~2017-07-26 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 14:54 Wenzhuo Lu
2017-07-26 15:17 ` Dumitrescu, Cristian
2017-07-31 16:53   ` Thomas Monjalon
2017-07-26 15:20 ` Wiles, Keith [this message]
2017-07-26 15:21   ` Wiles, Keith

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=7C6EB08A-CFB3-4631-9B02-3892E209E5C3@intel.com \
    --to=keith.wiles@intel.com \
    --cc=dev@dpdk.org \
    --cc=wenzhuo.lu@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).