From: David Marchand <david.marchand@6wind.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Maxime Leroy <maxime.leroy@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] eal: fix log level/type retrieving on a standard pthread
Date: Tue, 17 May 2016 17:56:44 +0200 [thread overview]
Message-ID: <CALwxeUv6qFHQHpi+=KeA4JX4YQRSSC=3F+v3Hum_oTRExDWTNg@mail.gmail.com> (raw)
In-Reply-To: <1462810416-6183-1-git-send-email-olivier.matz@6wind.com>
On Mon, May 9, 2016 at 6:13 PM, Olivier Matz <olivier.matz@6wind.com> wrote:
> From: Maxime Leroy <maxime.leroy@6wind.com>
>
> The functions rte_log_cur_msg_loglevel() and rte_log_cur_msg_logtype()
> return the current log level/type for the message being processed. They
> are used when implementing a user-defined logging stream.
>
> The current log levels and types were stored in a table indexed by the
> lcore_id, only returning a valid value for dataplane threads. Setting
> and getting these values in a non dataplane thread was ignored, using
> the global value instead.
>
> To fix this issue, a per-thread variable could be used (with
> RTE_DEFINE_PER_LCORE), allowing any pthread to set and retrieve its
> current log level or type.
>
> Signed-off-by: Maxime Leroy <maxime.leroy@6wind.com>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
Acked-by: David Marchand <david.marchand@6wind.com>
--
David Marchand
next prev parent reply other threads:[~2016-05-17 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 16:13 Olivier Matz
2016-05-11 16:39 ` Ferruh Yigit
2016-05-12 9:22 ` Olivier MATZ
2016-05-17 15:56 ` David Marchand [this message]
2016-05-18 14:50 ` Thomas Monjalon
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='CALwxeUv6qFHQHpi+=KeA4JX4YQRSSC=3F+v3Hum_oTRExDWTNg@mail.gmail.com' \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=maxime.leroy@6wind.com \
--cc=olivier.matz@6wind.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).