[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170226.154544.2016858795928257220.davem@davemloft.net>
Date: Sun, 26 Feb 2017 15:45:44 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: eric.dumazet@...il.com
Cc: netdev@...r.kernel.org, eugenia@...lanox.com, tariqt@...lanox.com
Subject: Re: [PATCH net] net/mlx4_en: fix overflow in
mlx4_en_init_timestamp()
From: Eric Dumazet <eric.dumazet@...il.com>
Date: Thu, 23 Feb 2017 15:22:43 -0800
> From: Eric Dumazet <edumazet@...gle.com>
>
> The cited commit makes a great job of finding optimal shift/multiplier
> values assuming a 10 seconds wrap around, but forgot to change the
> overflow_period computation.
>
> It overflows in cyclecounter_cyc2ns(), and the final result is 804 ms,
> which is silly.
>
> Lets simply use 5 seconds, no need to recompute this, given how it is
> supposed to work.
>
> Later, we will use a timer instead of a work queue, since the new RX
> allocation schem will no longer need mlx4_en_recover_from_oom() and the
> service_task firing every 250 ms.
>
> Fixes: 31c128b66e5b ("net/mlx4_en: Choose time-stamping shift value according to HW frequency")
> Signed-off-by: Eric Dumazet <edumazet@...gle.com>
Applied, thanks.
Powered by blists - more mailing lists