Re: [Intel-wired-lan] [PATCH] e1000e: changed some expensive calls of udelay to usleep_range

2017-09-08 Thread Pavel Machek
liams, Mitch A > > ; linux-ker...@vger.kernel.org; > > john.ronc...@intel.com; intel-wired-...@lists.osuosl.org; > > netdev@vger.kernel.org > > Subject: Re: [Intel-wired-lan] [PATCH] e1000e: changed some expensive calls > > of udelay to usleep_range > > > > Hi! > >

RE: [Intel-wired-lan] [PATCH] e1000e: changed some expensive calls of udelay to usleep_range

2017-09-07 Thread Brown, Aaron F
ntel.com; intel-wired-...@lists.osuosl.org; > netdev@vger.kernel.org > Subject: Re: [Intel-wired-lan] [PATCH] e1000e: changed some expensive calls > of udelay to usleep_range > > Hi! > > > @@ -183,7 +183,7 @@ s32 e1000e_read_phy_reg_mdic(struct e1000_hw > *hw, u32 offset, u16 *data) &g

Re: [Intel-wired-lan] [PATCH] e1000e: changed some expensive calls of udelay to usleep_range

2017-09-04 Thread Paul Menzel
Dear Matthew, On 08/23/17 17:59, Matthew Tan wrote: Calls to udelay are not preemtable by userspace so userspace applications experience a large (~200us) latency when running on core 0. Instead usleep_range can be used to be more friendly to userspace since it is preemtable.

Re: [Intel-wired-lan] [PATCH] e1000e: changed some expensive calls of udelay to usleep_range

2017-08-29 Thread Neftin, Sasha
On 8/23/2017 18:59, Matthew Tan wrote: Calls to udelay are not preemtable by userspace so userspace applications experience a large (~200us) latency when running on core 0. Instead usleep_range can be used to be more friendly to userspace since it is preemtable. This is due to