netdev - Re: [Patch net-next v2] net: add a generic tracepoint for TX queue timeout

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190502070601.GD2251@nanopsycho>
Date:   Thu, 2 May 2019 09:06:01 +0200
From:   Jiri Pirko <jiri@...nulli.us>
To:     Cong Wang <xiyou.wangcong@...il.com>
Cc:     netdev@...r.kernel.org, Eran Ben Elisha <eranbe@...lanox.com>,
        Jiri Pirko <jiri@...lanox.com>
Subject: Re: [Patch net-next v2] net: add a generic tracepoint for TX queue
 timeout

Thu, May 02, 2019 at 04:56:59AM CEST, xiyou.wangcong@...il.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 is useful to have a
>generic tracepoint to monitor this kind of TX timeout. We have
>been suffering TX timeout with different drivers, we plan to
>start to monitor it with rasdaemon which just needs a new tracepoint.
>
>Sample output:
>
>  ksoftirqd/1-16    [001] ..s2   144.043173: net_dev_xmit_timeout: dev=ens3 driver=e1000 queue=0
>
>Cc: Eran Ben Elisha <eranbe@...lanox.com>
>Cc: Jiri Pirko <jiri@...lanox.com>
>Signed-off-by: Cong Wang <xiyou.wangcong@...il.com>

Useful. Thanks!

Acked-by: Jiri Pirko <jiri@...lanox.com>