Re: [dpdk-dev] [PATCH] net/qede: fix slow path completion timeout

2018-05-25 Thread Ferruh Yigit
On 5/24/2018 7:02 PM, Mody, Rasesh wrote: > Hi Ferruh, > >> From: Ferruh Yigit [mailto:ferruh.yi...@intel.com] >> Sent: Thursday, May 24, 2018 10:22 AM >> >> On 5/23/2018 7:48 PM, Rasesh Mody wrote: >>> From: Shahed Shaikh >>> >>> In 100G mode, we poll firmware slow path completion for every 1 >>

Re: [dpdk-dev] [PATCH] net/qede: fix slow path completion timeout

2018-05-24 Thread Mody, Rasesh
Hi Ferruh, > From: Ferruh Yigit [mailto:ferruh.yi...@intel.com] > Sent: Thursday, May 24, 2018 10:22 AM > > On 5/23/2018 7:48 PM, Rasesh Mody wrote: > > From: Shahed Shaikh > > > > In 100G mode, we poll firmware slow path completion for every 1 > > second, which is not enough and may result in c

Re: [dpdk-dev] [PATCH] net/qede: fix slow path completion timeout

2018-05-24 Thread Ferruh Yigit
On 5/23/2018 7:48 PM, Rasesh Mody wrote: > From: Shahed Shaikh > > In 100G mode, we poll firmware slow path completion for every 1 second, > which is not enough and may result in completion timeout if > driver misses that window. > > Patch "eal: set affinity for control threads" exposed this iss

[dpdk-dev] [PATCH] net/qede: fix slow path completion timeout

2018-05-23 Thread Rasesh Mody
From: Shahed Shaikh In 100G mode, we poll firmware slow path completion for every 1 second, which is not enough and may result in completion timeout if driver misses that window. Patch "eal: set affinity for control threads" exposed this issue since alarm callback runs in control thread context.