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
| ||
|
Message-Id: <20190504.004349.367133794422105963.davem@davemloft.net> Date: Sat, 04 May 2019 00:43:49 -0400 (EDT) From: David Miller <davem@...emloft.net> To: xiyou.wangcong@...il.com Cc: netdev@...r.kernel.org, eranbe@...lanox.com, jiri@...lanox.com Subject: Re: [Patch net-next v2] net: add a generic tracepoint for TX queue timeout From: Cong Wang <xiyou.wangcong@...il.com> 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 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> Applied, thanks Cong.
Powered by blists - more mailing lists