Soft Patch Panel
 help / color / mirror / Atom feed
From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/3] Add utility functions for debug log
Date: Fri, 21 Dec 2018 13:10:38 +0900	[thread overview]
Message-ID: <1545365441-9864-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)

From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>

Hi,

Dynamic logging of DPDK is useful to configure log level only for
required modules. However, it is a little complex to use, for example,
for changing log level of type of `user*` simply to RTE_LOG_DEBUG.

This update is to add utility functions to change the log level of
`user*` in more simple way. If you change the level of RTE_LOGTYPE_USER1
to RTE_LOG_DEBUG, simply call `set_user_log_debug(1)`. You are also able
to change to any of log level like as
`set_user_log_level(1, RTE_LOG_INFO)`.

Default global log level is RTE_LOG_INFO, so you should change global
level with `--log-level` option of EAL from command line or call
`rte_log_set_global_level()` from inside of your program. 

Thanks,
Yasufumi

Yasufumi Ogawa (3):
  shared: add util functions to set log level
  primary: change dynamic log level to RTE_LOG_DEBUG
  spp_nfv: change dynamic log level to RTE_LOG_DEBUG

 src/nfv/nfv.c       |  2 ++
 src/primary/main.c  |  2 ++
 src/shared/common.c | 37 ++++++++++++++++++++++++++++++++++++-
 src/shared/common.h |  6 ++++++
 4 files changed, 46 insertions(+), 1 deletion(-)

-- 
2.7.4

             reply	other threads:[~2018-12-21  4:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21  4:10 ogawa.yasufumi [this message]
2018-12-21  4:10 ` [spp] [PATCH 1/3] shared: add util functions to set log level ogawa.yasufumi
2018-12-21  4:10 ` [spp] [PATCH 2/3] primary: change dynamic log level to RTE_LOG_DEBUG ogawa.yasufumi
2018-12-21  4:10 ` [spp] [PATCH 3/3] spp_nfv: " ogawa.yasufumi

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=1545365441-9864-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp \
    --to=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=ferruh.yigit@intel.com \
    --cc=spp@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).