All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Joongi Kim <joongi@an.kaist.ac.kr>
Cc: dev@dpdk.org
Subject: Re: Too verbose PMD init logs - intended or not?
Date: Wed, 13 May 2015 11:13:29 +0200	[thread overview]
Message-ID: <2261724.ecphA4QphE@xps13> (raw)
In-Reply-To: <CAKOGY8Jih5ajOjneQD85ZTa=gj8rPWf2DgJJe=SgsuLTOE+gLQ@mail.gmail.com>

Hi,

2015-05-13 08:47, Joongi Kim:
> Hello,
> I found that the following commit and post are conflicting with each other:
> 1)
> http://dpdk.org/browse/dpdk/commit/?id=23f91f32f2b119f1376488d87be2b80b078a945e
> 2) http://dpdk.org/ml/archives/dev/2015-April/016361.html
> Is there a consensus on how verbose PMD init processes should be?
> (i.e., Is this an intended behavior or a bug?)

Yes, debug logs should use the debug level. Simple :)

> I'd like to see if my ports are initialized, but not what memory addresses
> they are attached for each ring. (Most of PMD init logs are only useful
> when debugging!)
> 
> My configuration (.config) says CONFIG_RTE_LIBRTE_IXGBE_DEBUG_INIT=n and my
> program explicitly set the debug level to INFO by calling
> rte_set_log_level(), but *still* the ixgbe pmd generates a lot of
> PMD_INIT_LOG(DEBUG, ...) messages.

I guess you are not using the HEAD.
This commit should solve your problem:
	http://dpdk.org/browse/dpdk/commit/?id=23e4bf20a16d34

> For workaround, I'm currently roll-backing the commit 23f91f3 manually for
> my build and then it becomes silent.

Please confirm it's fixed in HEAD.

  reply	other threads:[~2015-05-13  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  8:47 Too verbose PMD init logs - intended or not? Joongi Kim
2015-05-13  9:13 ` Thomas Monjalon [this message]
2015-05-13 12:00   ` Joongi Kim

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=2261724.ecphA4QphE@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=joongi@an.kaist.ac.kr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.