From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] Too much print of testpmd
Date: Thu, 27 Apr 2017 00:51:37 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B59CF9A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20170426090501.GV14914@bidouze.vm.6wind.com>
Hi Gaëtan,
> -----Original Message-----
> From: Gaëtan Rivet [mailto:gaetan.rivet@6wind.com]
> Sent: Wednesday, April 26, 2017 5:05 PM
> To: Lu, Wenzhuo
> Cc: dev@dpdk.org; Wu, Jingjing
> Subject: Re: Too much print of testpmd
>
> Hi Wenzhuo,
>
> On Wed, Apr 26, 2017 at 05:10:44AM +0000, Lu, Wenzhuo wrote:
> > Hi Gaetan,
> >
> > When using DPDK PF + DPDK VF, there's too much print like,
> >
> > Port 0: VF Mbox event
> >
> >
> >
> > Seems it's not good to print every event directly. If it's necessary, is
> > it better to redirect the output to a log file?
> >
> > Thanks.
> >
>
> I'm not convinced of the logfile solution. I'd like to keep it simple and
> contained. Logfile means having to provide a name, or use a default one
> with several drawbacks, and a pretty leaky design.
>
> I will add a handle mask that will enable or disable this logging feature. The
> default mask would then enable it for LSC and other such sporadic events,
> while disabling it for the VF Mbox one. It will be able to be fine-tuned and
> configured at runtime by a parameter and/or testpmd command.
>
> I'll propose it soon.
Agree. Log file may be too heavy. The switches for the print is good enough.
>
> >
> >
> >
> >
> > Best regards
> >
> > Wenzhuo Lu
> >
> >
>
> --
> Gaëtan Rivet
> 6WIND
prev parent reply other threads:[~2017-04-27 0:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 5:10 Lu, Wenzhuo
2017-04-26 9:05 ` Gaëtan Rivet
2017-04-27 0:51 ` Lu, Wenzhuo [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=6A0DE07E22DDAD4C9103DF62FEBC09093B59CF9A@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=jingjing.wu@intel.com \
/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).