patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: David Marchand <david.marchand@redhat.com>,
	dev@dpdk.org, stable@dpdk.org, Anoob Joseph <anoobj@marvell.com>
Subject: Re: [PATCH] doc: enhance the global log level documentation
Date: Wed, 9 Oct 2024 11:50:39 -0700	[thread overview]
Message-ID: <20241009115039.7b506205@hermes.local> (raw)
In-Reply-To: <b5cf5c81-3fa6-4580-b383-2fc5ad5b27c1@ovn.org>

On Wed, 26 Jun 2024 19:10:48 +0200
Ilya Maximets <i.maximets@ovn.org> wrote:

> On 6/26/24 17:09, David Marchand wrote:
> > The current documentation is non intuitive in that the global log level
> > can be understood as being a single knob controlling all components
> > logs.
> > On the contrary, all the global log level is for is to reduce verbosity
> > globally.
> > 
> > Remove examples of setting --log-level=8|debug, which is a noop.
> > 
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > ---

Yes, the global log level pre-dates the introduction of component logs.

The wording would be better if it was more precise.

Something like:

By default, all log messages enabled by a particular component are visible.
But this may be too verbose. For example, to suppress all logs below warning level:
      
	/path/to-app --log-level=warning


      reply	other threads:[~2024-10-09 18:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 15:09 David Marchand
2024-06-26 17:10 ` Ilya Maximets
2024-10-09 18:50   ` Stephen Hemminger [this message]

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=20241009115039.7b506205@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=anoobj@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=i.maximets@ovn.org \
    --cc=stable@dpdk.org \
    /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).