From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v6 2/2] app/testpmd: fix port stop
Date: Fri, 10 Mar 2017 14:17:54 +0100 [thread overview]
Message-ID: <6179789.zosxSocSkF@xps13> (raw)
In-Reply-To: <9BB6961774997848B5B42BEC655768F810CD9A71@SHSMSX103.ccr.corp.intel.com>
2017-02-12 04:34, Wu, Jingjing:
> > > > --- a/app/test-pmd/testpmd.c
> > > > +++ b/app/test-pmd/testpmd.c
> > > > @@ -1490,13 +1490,13 @@ stop_port(portid_t pid)
> > > > continue;
> > > > }
> > > >
> > > > + rte_eth_dev_stop(pi);
> > > > +
> > > > port = &ports[pi];
> > > > if (rte_atomic16_cmpset(&(port->port_status),
> > > > RTE_PORT_STARTED,
> > > > RTE_PORT_HANDLING) == 0)
> > > > continue;
> > > >
> > > > - rte_eth_dev_stop(pi);
> > > > -
> > >
> > > I don't think this fix is correct to move rte_eth_dev_stop above.
> > >
> > > We need to make sure rte_eth_dev_start is called in start_port. For
> > > vmdq configuration, You just need to change the configuration when
> > > port is stopped.
> >
> > I think the stop_port() function should always stop the port even if the
> > port_status is not correct for any reason.
> > At present stop_port() returns without stopping the port if the port_status is not
> > RTE_PORT_STARTED.
> >
> This is testpmd's design. If you think it is an issue, maybe you need to prepare patch to optimize it. But for VMDQ configuration, I'd like to make it independent but not mixed.
>
> > The VMDq configuration is done whet the port is stopped, however to the
> > complete the VMDq configuration the port must be started.
> >
>
> To change minor, we can stop port, then configure VMDQ and then start port.
>
> You make port started in VMDQ config, the Symmetry of stop/start command is broken and it is not easy to maintain.
Should we close this patch in patchwork?
next prev parent reply other threads:[~2017-03-10 13:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 16:29 [dpdk-dev] [PATCH v2 0/2] net/i40e: fix segmentation fault Bernard Iremonger
2017-01-09 16:29 ` [dpdk-dev] [PATCH v2 1/2] net/i40e: fix segmentation fault in close Bernard Iremonger
2017-01-09 16:29 ` [dpdk-dev] [PATCH v2 2/2] app/testpmd: add command to configure VMDq Bernard Iremonger
2017-01-12 13:58 ` [dpdk-dev] [PATCH v3 0/2] net/i40e: fix segmentation fault Bernard Iremonger
2017-01-17 16:39 ` [dpdk-dev] [PATCH v4 " Bernard Iremonger
2017-01-25 14:36 ` [dpdk-dev] [PATCH v5 0/3] " Bernard Iremonger
2017-01-27 10:49 ` [dpdk-dev] [PATCH v6 0/2] app/testpmd: enable VMDq in testpmd Bernard Iremonger
2017-01-27 10:49 ` [dpdk-dev] [PATCH v6 1/2] app/testpmd: add command to configure VMDq Bernard Iremonger
2017-01-27 10:50 ` [dpdk-dev] [PATCH v6 2/2] app/testpmd: fix port stop Bernard Iremonger
2017-02-03 8:21 ` Wu, Jingjing
2017-02-03 10:37 ` Iremonger, Bernard
2017-02-12 4:34 ` Wu, Jingjing
2017-03-10 13:17 ` Thomas Monjalon [this message]
2017-03-10 16:56 ` Wu, Jingjing
2017-03-10 16:59 ` Iremonger, Bernard
2017-01-25 14:36 ` [dpdk-dev] [PATCH v5 1/3] net/i40e: fix segmentation fault in close Bernard Iremonger
2017-01-25 14:36 ` [dpdk-dev] [PATCH v5 2/3] app/testpmd: add command to configure VMDq Bernard Iremonger
2017-01-25 14:36 ` [dpdk-dev] [PATCH v5 3/3] app/testpmd: fix port stop Bernard Iremonger
2017-01-17 16:39 ` [dpdk-dev] [PATCH v4 1/2] net/i40e: fix segmentation fault in close Bernard Iremonger
2017-01-20 13:15 ` Wu, Jingjing
2017-01-17 16:39 ` [dpdk-dev] [PATCH v4 2/2] app/testpmd: add command to configure VMDq Bernard Iremonger
2017-01-20 13:33 ` Wu, Jingjing
2017-01-20 15:22 ` Iremonger, Bernard
2017-01-12 13:58 ` [dpdk-dev] [PATCH v3 1/2] net/i40e: fix segmentation fault in close Bernard Iremonger
2017-01-17 14:34 ` Wu, Jingjing
2017-01-17 16:30 ` Iremonger, Bernard
2017-01-12 13:58 ` [dpdk-dev] [PATCH v3 2/2] app/testpmd: add command to configure VMDq Bernard Iremonger
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=6179789.zosxSocSkF@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@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).