From: Cong Wang
Date: Wed, 1 May 2019 19:56:59 -0700
> Although devlink health report does a nice job on reporting TX
> timeout and other NIC errors, unfortunately it requires drivers
> to support it but currently only mlx5 has implemented it.
> Before other drivers could catch up, it is useful
On 5/2/2019 5:56 AM, Cong Wang wrote:
> Although devlink health report does a nice job on reporting TX
> timeout and other NIC errors, unfortunately it requires drivers
> to support it but currently only mlx5 has implemented it.
> Before other drivers could catch up, it is useful to have a
> gene
Thu, May 02, 2019 at 04:56:59AM CEST, xiyou.wangc...@gmail.com wrote:
>Although devlink health report does a nice job on reporting TX
>timeout and other NIC errors, unfortunately it requires drivers
>to support it but currently only mlx5 has implemented it.
>Before other drivers could catch up, it
Although devlink health report does a nice job on reporting TX
timeout and other NIC errors, unfortunately it requires drivers
to support it but currently only mlx5 has implemented it.
Before other drivers could catch up, it is useful to have a
generic tracepoint to monitor this kind of TX timeout.
