2015-06-24 15:56, Michael Qiu:
> When close one port twice, testpmd will give out wrong messagse.
>
> testpmd> port stop 0
> Stopping ports...
> Checking link statuses...
> Port 0 Link Up - speed 0 Mbps - full-duplex
> Port 1 Link Up - speed 0 Mbps - full-duplex
> Done
> testpmd> port close 0
> C
On 2015/7/8 2:04, Richardson, Bruce wrote:
> On Wed, Jul 08, 2015 at 07:16:21AM +, Qiu, Michael wrote:
[.../...]
>>> port = &ports[pi];
>>> if (rte_atomic16_cmpset(&(port->port_status),
>>> + RTE_PORT_CLOSED, RTE_PORT_CLOSED) == 1) {
>>> +
On Wed, Jul 08, 2015 at 07:16:21AM +, Qiu, Michael wrote:
> Any comments? This is a bug fix, not a feature.
>
> Thanks,
> Michael
>
> On 6/24/2015 3:56 PM, Qiu, Michael wrote:
> > When close one port twice, testpmd will give out wrong messagse.
> >
> > testpmd> port stop 0
> > Stopping ports
Any comments? This is a bug fix, not a feature.
Thanks,
Michael
On 6/24/2015 3:56 PM, Qiu, Michael wrote:
> When close one port twice, testpmd will give out wrong messagse.
>
> testpmd> port stop 0
> Stopping ports...
> Checking link statuses...
> Port 0 Link Up - speed 0 Mbps - full-duplex
> Po
When close one port twice, testpmd will give out wrong messagse.
testpmd> port stop 0
Stopping ports...
Checking link statuses...
Port 0 Link Up - speed 0 Mbps - full-duplex
Port 1 Link Up - speed 0 Mbps - full-duplex
Done
testpmd> port close 0
Closing ports...
Done
testpmd> port close 0
Closing
5 matches
Mail list logo