From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: Ilya Maximets <i.maximets@ovn.org>,
stable@dpdk.org, Anoob Joseph <anoobj@marvell.com>
Subject: [PATCH] doc: enhance the global log level documentation
Date: Wed, 26 Jun 2024 17:09:25 +0200 [thread overview]
Message-ID: <20240626150926.1918948-1-david.marchand@redhat.com> (raw)
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>
---
doc/guides/cryptodevs/octeontx.rst | 2 +-
doc/guides/prog_guide/log_lib.rst | 10 ++++++----
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/doc/guides/cryptodevs/octeontx.rst b/doc/guides/cryptodevs/octeontx.rst
index a39f3f3d02..97e13514f3 100644
--- a/doc/guides/cryptodevs/octeontx.rst
+++ b/doc/guides/cryptodevs/octeontx.rst
@@ -114,7 +114,7 @@ OCTEON TX crypto PMD.
.. code-block:: console
- ./build/ipsec-secgw --log-level=8 -c 0xff -- -P -p 0x3 -u 0x2 --config
+ ./build/ipsec-secgw -c 0xff -- -P -p 0x3 -u 0x2 --config
"(1,0,0),(0,0,0)" -f ep1.cfg
Testing
diff --git a/doc/guides/prog_guide/log_lib.rst b/doc/guides/prog_guide/log_lib.rst
index ff9d1b54a2..965b7e9961 100644
--- a/doc/guides/prog_guide/log_lib.rst
+++ b/doc/guides/prog_guide/log_lib.rst
@@ -32,18 +32,20 @@ or by the user passing the ``--log-level`` parameter to the EAL via the applicat
Setting Global Log Level
~~~~~~~~~~~~~~~~~~~~~~~~
-To adjust the global log level for an application,
-just pass a numeric level or a level name to the ``--log-level`` EAL parameter.
+By default, the global log level is set to ``RTE_LOG_DEBUG``.
+
+To reduce the verbosity of an application globally,
+adjust the global log level by passing a numeric level or a level name to the ``--log-level`` EAL parameter.
For example::
/path/to/app --log-level=error
- /path/to/app --log-level=debug
-
/path/to/app --log-level=5 # warning
Within an application, the log level can be similarly set using the ``rte_log_set_global_level`` API.
+For setting per component log levels, see below.
+
Setting Log Level for a Component
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
2.45.2
next reply other threads:[~2024-06-26 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 15:09 David Marchand [this message]
2024-06-26 17:10 ` Ilya Maximets
2024-10-09 18:50 ` Stephen Hemminger
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=20240626150926.1918948-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=anoobj@marvell.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).