From: Bing Zhao <bingz@nvidia.com>
To: David Marchand <david.marchand@redhat.com>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] ethdev: fix log level of Tx and Rx dummy functions
Date: Tue, 26 Oct 2021 03:18:55 +0000 [thread overview]
Message-ID: <DM5PR12MB1755CE744207746AD98B43CED0849@DM5PR12MB1755.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8yq0Ypb6P+P97cfqQTft=Xb2+nErCo9evti4ETrpm5VWg@mail.gmail.com>
Hi David,
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Monday, October 25, 2021 9:32 PM
> To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
> Cc: Ananyev, Konstantin <konstantin.ananyev@intel.com>; Bing Zhao
> <bingz@nvidia.com>; Yigit, Ferruh <ferruh.yigit@intel.com>;
> andrew.rybchenko@oktetlabs.ru; dev@dpdk.org
> Subject: Re: [PATCH 1/2] ethdev: fix log level of Tx and Rx dummy
> functions
>
> External email: Use caution opening links or attachments
>
>
> On Mon, Oct 25, 2021 at 3:27 PM Thomas Monjalon <thomas@monjalon.net>
> wrote:
> > > > > There is a concern about getting efficient log report,
> > > > > especially when looking at CI issues.
> > > >
> > > > +1.
> > > > The current solution with logs is a real pain.
> > >
> > > Are you guys talking about problems with
> > > app/test/sample_packet_forward.* David reported?
> > > Or some extra problems arise?
> >
> > The problem will arise each time an app is misbehaving.
> > That's going to be a recurring problem in the CI.
> >
>
> One thing that could be done is compiling with asserts in CI, and
> let default build not have those asserts.
>
> Otherwise, logging once should be enough (I have a patch for this
> latter idea).
If you already have a patch to log once, I will suppress this patch. Thanks
>
>
> --
> David Marchand
BR. Bing
next prev parent reply other threads:[~2021-10-26 3:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 21:14 Bing Zhao
2021-10-22 21:14 ` [dpdk-dev] [PATCH 2/2] ethdev: fix the race condition for fp ops reset Bing Zhao
2021-10-23 8:34 ` Thomas Monjalon
2021-10-23 11:39 ` Ananyev, Konstantin
2021-11-10 14:34 ` Ferruh Yigit
2021-11-10 14:37 ` Ananyev, Konstantin
2021-11-10 14:57 ` Thomas Monjalon
2021-11-10 15:24 ` Bing Zhao
2021-10-23 16:13 ` [dpdk-dev] " Stephen Hemminger
2021-10-24 5:54 ` Bing Zhao
2021-10-23 8:32 ` [dpdk-dev] [PATCH 1/2] ethdev: fix log level of Tx and Rx dummy functions Thomas Monjalon
2021-10-23 11:46 ` Ananyev, Konstantin
2021-10-23 12:45 ` Bing Zhao
2021-10-24 11:48 ` Ananyev, Konstantin
2021-10-25 9:43 ` Thomas Monjalon
2021-10-25 9:51 ` David Marchand
2021-10-25 12:55 ` Ananyev, Konstantin
2021-10-25 13:27 ` Thomas Monjalon
2021-10-25 13:31 ` David Marchand
2021-10-25 20:29 ` Ananyev, Konstantin
2021-10-25 20:38 ` Thomas Monjalon
2021-10-26 12:38 ` Ananyev, Konstantin
2021-10-26 12:59 ` Thomas Monjalon
2021-10-26 3:18 ` Bing Zhao [this message]
2021-10-23 12:12 ` Bing Zhao
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=DM5PR12MB1755CE744207746AD98B43CED0849@DM5PR12MB1755.namprd12.prod.outlook.com \
--to=bingz@nvidia.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=thomas@monjalon.net \
/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).