Netdev List
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, Eran Ben Elisha <eranbe@mellanox.com>,
	Jiri Pirko <jiri@mellanox.com>
Subject: Re: [Patch net-next v2] net: add a generic tracepoint for TX queue timeout
Date: Thu, 2 May 2019 09:06:01 +0200	[thread overview]
Message-ID: <20190502070601.GD2251@nanopsycho> (raw)
In-Reply-To: <20190502025659.30351-1-xiyou.wangcong@gmail.com>

Thu, May 02, 2019 at 04:56:59AM CEST, xiyou.wangcong@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 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@mellanox.com>
>Cc: Jiri Pirko <jiri@mellanox.com>
>Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>

Useful. Thanks!

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

  reply	other threads:[~2019-05-02  7:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02  2:56 [Patch net-next v2] net: add a generic tracepoint for TX queue timeout Cong Wang
2019-05-02  7:06 ` Jiri Pirko [this message]
2019-05-02  8:44 ` Eran Ben Elisha
2019-05-04  4:43 ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190502070601.GD2251@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=eranbe@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox