From: Tiwei Bie <tiwei.bie@intel.com>
To: Adrian Moreno <amorenoz@redhat.com>
Cc: dev@dpdk.org, zhihong.wang@intel.com, maxime.coquelin@redhat.com,
huawei.xie@intel.com
Subject: Re: [dpdk-dev] [RFC PATCH 1/1] vhost: Add dynamic logging system
Date: Tue, 29 Oct 2019 21:45:43 +0800 [thread overview]
Message-ID: <20191029134543.GA20281@___> (raw)
In-Reply-To: <20191018082638.4463-2-amorenoz@redhat.com>
On Fri, Oct 18, 2019 at 10:26:39AM +0200, Adrian Moreno wrote:
> Currently there are a couple of limitations on the logging system: Most
> of the logs are compiled out and both datapath and controlpath logs
> share the same loglevel.
>
> This patch tries to help fix that situation by:
> - Splitting control plane and data plane logs
> - Making control plane logs dynamic while keeping data plane logs
> compiled out by default for log levels lower than RTE_LOG_DP_LEVEL.
+1
Thanks for the work!
Thanks,
Tiwei
prev parent reply other threads:[~2019-10-29 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 8:26 [dpdk-dev] [RFC PATCH 0/1] vhost: Add dynamic log tracing Adrian Moreno
2019-10-18 8:26 ` [dpdk-dev] [RFC PATCH 1/1] vhost: Add dynamic logging system Adrian Moreno
2019-10-29 13:45 ` Tiwei Bie [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=20191029134543.GA20281@___ \
--to=tiwei.bie@intel.com \
--cc=amorenoz@redhat.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=zhihong.wang@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).