[dpdk-dev] [PATCH] librte: Link status interrupt race condition, IGB E1000

2015-10-27 Thread Thomas Monjalon
2015-10-26 05:25, Lu, Wenzhuo: > I think you're right. To my opinion, this if is added to avoid the race > condition. So, it should be " dev->data->dev_conf.intr_conf.lsc == 0". It > means if the interrupts are not enabled, we'd update the link when starting, > if not we can leave it the interru

[dpdk-dev] [PATCH] librte: Link status interrupt race condition, IGB E1000

2015-10-26 Thread Lu, Wenzhuo
Hi Tim, > -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Monday, October 26, 2015 6:56 AM > To: Lu, Wenzhuo > Cc: dev at dpdk.org; Tim Shearer > Subject: Re: [dpdk-dev] [PATCH] librte: Link status interrupt race condition, > I

[dpdk-dev] [PATCH] librte: Link status interrupt race condition, IGB E1000

2015-10-25 Thread Thomas Monjalon
Wenzhuo, Please could you have a look? Thanks 2015-09-24 20:44, Tim Shearer: > I encountered an issue with DPDK 2.1.0 which occasionally causes the link > status interrupt callback not to be called after the interface is started for > the first time. I traced the problem back to the function >

[dpdk-dev] [PATCH] librte: Link status interrupt race condition, IGB E1000

2015-09-24 Thread Tim Shearer
I encountered an issue with DPDK 2.1.0 which occasionally causes the link status interrupt callback not to be called after the interface is started for the first time. I traced the problem back to the function eth_igb_link_update(), which is used to determine if the link has changed state sinc