On Wed, Jun 26, 2019 at 5:25 AM Sudarsana Reddy Kalluru
wrote:
> > Sudarsana, let me ask you something: why does the register is reading value
> > 0x0 always in the TX timestamp routine if the RX filter is set to None?
> > This is
> > the main cause of the thread reschedule thing.
>
> The registe
> -Original Message-
> From: Guilherme Piccoli
> Sent: Wednesday, June 26, 2019 1:56 AM
> To: Sudarsana Reddy Kalluru ;
> jay.vosbu...@canonical.com
> Cc: GR-everest-linux-l2 ;
> netdev@vger.kernel.org; Ariel Elior
> Subject: Re: [EXT] [PATCH V2] bnx2x: Prevent pt
Sudarsana, let me ask you something: why does the register is reading
value 0x0 always in the
TX timestamp routine if the RX filter is set to None? This is the main
cause of the thread reschedule
thing.
Of course this thread thing is important to fix, but I was discussing
with my leader here and w
On Tue, Jun 25, 2019 at 1:02 AM Sudarsana Reddy Kalluru
wrote:
>
> Thanks for your changes and time on this. In general time-latching happens in
> couple or more milliseconds (even in some 100s of usec) under the normal
> traffic conditions. With this approach, there's a possibility that every
> -Original Message-
> From: Guilherme G. Piccoli
> Sent: Tuesday, June 25, 2019 3:54 AM
> To: GR-everest-linux-l2 ;
> netdev@vger.kernel.org; Sudarsana Reddy Kalluru
> Cc: Ariel Elior ; gpicc...@canonical.com;
> jay.vosbu...@canonical.com
> Subject: [EXT] [
