* [dpdk-dev] ethdev: fix link status race condition
@ 2016-01-17 16:51 Yaacov Hazan
0 siblings, 0 replies; only message in thread
From: Yaacov Hazan @ 2016-01-17 16:51 UTC (permalink / raw)
To: Tim Shearer; +Cc: dev
Hi,
I looked in your patch ethdev: fix link status race condition (d5790b03), and have a question.
According to your change when dev_start is called and the device supports lsc we doesn't ask the device status.
But, if the device is already up, when you start dpdk application, the application can't know that the status of the port is up since dev_start won't ask for the device status and no interrupt is trigger since no changed has been made (the device is already up).
Can you please explain the idea of this patch?
Thanks,
Yaacov.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-01-17 16:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-01-17 16:51 [dpdk-dev] ethdev: fix link status race condition Yaacov Hazan
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).