DPDK usage discussions
 help / color / mirror / Atom feed
From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] How to show debug log in DPDK and DPDK application
Date: Fri, 21 Dec 2018 15:42:12 +0900	[thread overview]
Message-ID: <201812210643.wBL6hXX5013986@ccmail04.silk.ntt-tx.co.jp> (raw)
In-Reply-To: <20181220191013.358bebd8@xeon-e3>

> On Fri, 21 Dec 2018 09:48:04 +0900
> Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp> wrote:
> 
> > Hello 
> > 
> > I am a developer for DPDK application(SPP).
> > And I have a very basic question how to debug by
> > increasing log level.
> > 
> > Q1.Are thre any documents those describe the following?
> > - how to output debug log of DPDK
> > - how to output debut log of DPDK application
> > 
> > As I did quick search on Google, no official documents found.
> > If above is yes.
> > Please let me know how to achieve those.
> > 
> > Thanks in advance for your guidance to newbie!
> > 
> > BR,
> > Hideyuki Yamashita
> > NTT TechnoCross
> > 
> > 
> 
> logging in current DPDK is controlled per subsystem.
> 
> See: rte_log_set_level_pattern and rte_set_level
> 
> This can be set on command line or with API.
> 
> The default log output on DPDK is to stdout of the application.
> This is not useful for a long running service like a daemon,
> but the log can be captured by either opening a file and using:
>  rte_openlog_stream
> 
> Or also by using glibc stdio function open_memstream to make a memory stream
> and pass that. This requires a bit more setup.
Hello Stephen,

Thaks for your guidance.
I will read those.

But at a glance, it looks like those are in API documents and 
I wondered if those are well documented in somewhere
in developers guide so that developers like me can 
easily find the path.

What do you think?

Thanks!

BR,
Hideyuki
NTT TechnoCross

  reply	other threads:[~2018-12-21  6:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 15:27 [dpdk-users] KNI jumbo support Liron Himi
2018-12-21  0:48 ` [dpdk-users] How to show debug log in DPDK and DPDK application Hideyuki Yamashita
2018-12-21  3:10   ` Stephen Hemminger
2018-12-21  6:42     ` Hideyuki Yamashita [this message]
2019-01-02 10:27 ` [dpdk-users] KNI jumbo support Ferruh Yigit

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=201812210643.wBL6hXX5013986@ccmail04.silk.ntt-tx.co.jp \
    --to=yamashita.hideyuki@po.ntt-tx.co.jp \
    --cc=stephen@networkplumber.org \
    --cc=users@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).