From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: fix port segmentation fault when restart
Date: Wed, 3 Jan 2018 06:10:54 +0000 [thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07C93F5E@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <039ED4275CED7440929022BC67E7061153123DC5@SHSMSX103.ccr.corp.intel.com>
Hi, zhangqi
> -----Original Message-----
> From: Zhang, Qi Z
> Sent: Friday, December 22, 2017 11:31 AM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Cc: Zhao1, Wei <wei.zhao1@intel.com>
> Subject: RE: [dpdk-dev] [PATCH v2] net/i40e: fix port segmentation fault
> when restart
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wei Zhao
> > Sent: Wednesday, November 15, 2017 1:55 PM
> > To: dev@dpdk.org
> > Cc: Zhao1, Wei <wei.zhao1@intel.com>
> > Subject: [dpdk-dev] [PATCH v2] net/i40e: fix port segmentation fault
> > when restart
> >
> > It will clear all queue region related configuration when dev stop
> > even if threr
>
> s/threr/there
>
> > is no queue region config, so this may cause error. So add check when
> > flush queue region config and delete it when device stop.
> >
> > Fixes: 7cbecc2f742 ("net/i40e: support queue region set and flush")
> >
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> >
> > ---
> >
> > v2:
> > -fix patch check warning.
> > ---
> > drivers/net/i40e/i40e_ethdev.c | 3 ---
> > drivers/net/i40e/rte_pmd_i40e.c | 27 ++++++++++++++-------------
> > 2 files changed, 14 insertions(+), 16 deletions(-)
> >
> > diff --git a/drivers/net/i40e/i40e_ethdev.c
> > b/drivers/net/i40e/i40e_ethdev.c index 811cc9f..7a1290b 100644
> > --- a/drivers/net/i40e/i40e_ethdev.c
> > +++ b/drivers/net/i40e/i40e_ethdev.c
> > @@ -2154,9 +2154,6 @@ i40e_dev_stop(struct rte_eth_dev *dev)
> > /* reset hierarchy commit */
> > pf->tm_conf.committed = false;
> >
> > - /* Remove all the queue region configuration */
> > - i40e_flush_queue_region_all_conf(dev, hw, pf, 0);
> > -
> From the commit log, the reason you remove above line is because the
> function can't handle the situation when no queue region config, but what
> about the case that queue region config does exist? Could you add more
> message to explain why this not be impacted.
Ok, I will add some more info about when queue region config does exist.
In this case, it treat no queue region config as queue region config does exist.
>
> > hw->adapter_stopped = 1;
> > }
> >
> > diff --git a/drivers/net/i40e/rte_pmd_i40e.c
> > b/drivers/net/i40e/rte_pmd_i40e.c index aeb92af..c2e2466 100644
> > --- a/drivers/net/i40e/rte_pmd_i40e.c
> > +++ b/drivers/net/i40e/rte_pmd_i40e.c
> > @@ -2845,22 +2845,23 @@ i40e_flush_queue_region_all_conf(struct
> > rte_eth_dev *dev,
> > return 0;
> > }
> >
> > - info->queue_region_number = 1;
> > - info->region[0].queue_num = main_vsi->nb_used_qps;
> > - info->region[0].queue_start_index = 0;
> > + if (info->queue_region_number) {
> > + info->queue_region_number = 1;
> > + info->region[0].queue_num = main_vsi->nb_used_qps;
> > + info->region[0].queue_start_index = 0;
> >
> > - ret = i40e_vsi_update_queue_region_mapping(hw, pf);
> > - if (ret != I40E_SUCCESS)
> > - PMD_DRV_LOG(INFO, "Failed to flush queue region
> mapping.");
> > -
> > - ret = i40e_dcb_init_configure(dev, TRUE);
> > - if (ret != I40E_SUCCESS) {
> > - PMD_DRV_LOG(INFO, "Failed to flush dcb.");
> > - pf->flags &= ~I40E_FLAG_DCB;
> > - }
> > + ret = i40e_vsi_update_queue_region_mapping(hw, pf);
> > + if (ret != I40E_SUCCESS)
> > + PMD_DRV_LOG(INFO, "Failed to flush queue region
> > mapping.");
>
> WARNING: line over 80 characters
There is a new rule that I has been told by Ferruh Yigit, log message in double quotation marks can over 80 characters.
> Regards
> Qi
>
> >
> > - i40e_init_queue_region_conf(dev);
> > + ret = i40e_dcb_init_configure(dev, TRUE);
> > + if (ret != I40E_SUCCESS) {
> > + PMD_DRV_LOG(INFO, "Failed to flush dcb.");
> > + pf->flags &= ~I40E_FLAG_DCB;
> > + }
> >
> > + i40e_init_queue_region_conf(dev);
> > + }
> > return 0;
> > }
> >
> > --
> > 2.7.4
next prev parent reply other threads:[~2018-01-03 6:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 5:46 [dpdk-dev] [PATCH] " Wei Zhao
2017-11-15 5:55 ` [dpdk-dev] [PATCH v2] " Wei Zhao
2017-12-22 3:30 ` Zhang, Qi Z
2018-01-03 6:10 ` Zhao1, Wei [this message]
2018-01-03 7:17 ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-01-03 8:19 ` Zhang, Qi Z
2018-01-13 6:04 ` Zhang, Helin
2018-01-12 6:59 ` [dpdk-dev] [PATCH v4] " Wei Zhao
2018-01-13 15:29 ` Zhang, Helin
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=A2573D2ACFCADC41BB3BE09C6DE313CA07C93F5E@PGSMSX103.gar.corp.intel.com \
--to=wei.zhao1@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).