From: "marcelo.leitner@gmail.com" <marcelo.leitner@gmail.com>
To: Saeed Mahameed <saeedm@mellanox.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"leon@kernel.org" <leon@kernel.org>,
Roi Dayan <roid@mellanox.com>, Paul Blakey <paulb@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Vlad Buslov <vladbu@mellanox.com>, Oz Shlomo <ozsh@mellanox.com>
Subject: Re: [PATCH net] net/mlx5e: limit log messages due to (ovs) probing to _once
Date: Wed, 8 Apr 2020 18:54:22 -0300 [thread overview]
Message-ID: <20200408215422.GA137894@localhost.localdomain> (raw)
In-Reply-To: <d4c0225fc25a6979c6f6863eaf84ee4d4d0a7972.camel@mellanox.com>
On Wed, Apr 08, 2020 at 07:51:22PM +0000, Saeed Mahameed wrote:
...
> > > I understand it is for debug only but i strongly suggest to not
> > > totally
> > > suppress these messages and maybe just move them to tracepoints
> > > buffer
> > > ? for those who would want to really debug ..
> > >
> > > we already have some tracepoints implemented for en_tc.c
> > > mlx5/core/diag/en_tc_tracepoints.c, maybe we should define a
> > > tracepoint
> > > for error reporting ..
> >
> > That, or s/netdev_warn/netdev_dbg/, but both are more hidden to the
> > user than the _once.
> >
>
> i don't see any reason to pollute kernel log with debug messages when
> we have tracepoint buffer for en_tc ..
So we're agreeing that these need to be changed. Good.
I don't think a sysadmin would be using tracepoints for
troubleshooting this, but okay. My only objective here is exactly what
you said, to not pollute kernel log too much with these potentially
repetitive messages.
next prev parent reply other threads:[~2020-04-08 21:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 0:11 [PATCH net] net/mlx5e: limit log messages due to (ovs) probing to _once Marcelo Ricardo Leitner
2020-04-03 2:27 ` Saeed Mahameed
2020-04-03 2:48 ` marcelo.leitner
2020-04-08 19:51 ` Saeed Mahameed
2020-04-08 21:54 ` marcelo.leitner [this message]
2020-04-08 22:38 ` Saeed Mahameed
2020-04-08 22:42 ` marcelo.leitner
2020-04-12 8:14 ` Roi Dayan
2020-04-13 6:35 ` Or Gerlitz
2020-04-13 14:29 ` Marcelo Ricardo Leitner
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=20200408215422.GA137894@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ozsh@mellanox.com \
--cc=paulb@mellanox.com \
--cc=roid@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=vladbu@mellanox.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;
as well as URLs for NNTP newsgroup(s).