From: Stephen Hemminger <stephen@networkplumber.org>
To: Aman Singh <aman.deep.singh@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: add log to print dpdk version at start
Date: Wed, 1 Sep 2021 10:12:53 -0700 [thread overview]
Message-ID: <20210901101253.6991a2f6@hermes.local> (raw)
In-Reply-To: <20210901061821.5259-1-aman.deep.singh@intel.com>
On Wed, 1 Sep 2021 11:48:21 +0530
Aman Singh <aman.deep.singh@intel.com> wrote:
> From the logs it is difficult to get the DPDK version
> that was used. So added a debug log to print the same.
> The log has been added in eal_init so it gets printed
> at startup for any application.
>
> Signed-off-by: Aman Singh <aman.deep.singh@intel.com>
> ---
> lib/eal/freebsd/eal.c | 2 +-
> lib/eal/linux/eal.c | 2 +-
> lib/eal/windows/eal.c | 1 +
> 3 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/lib/eal/freebsd/eal.c b/lib/eal/freebsd/eal.c
> index 6cee5ae369..a14a205f4d 100644
> --- a/lib/eal/freebsd/eal.c
> +++ b/lib/eal/freebsd/eal.c
> @@ -958,7 +958,7 @@ rte_eal_init(int argc, char **argv)
> }
>
> eal_mcfg_complete();
> -
> + rte_log(RTE_LOG_DEBUG, RTE_LOGTYPE_EAL, "DPDK version: %s\n", rte_version());
> return fctret;
> }
>
> diff --git a/lib/eal/linux/eal.c b/lib/eal/linux/eal.c
> index 3577eaeaa4..a50960cc78 100644
> --- a/lib/eal/linux/eal.c
> +++ b/lib/eal/linux/eal.c
> @@ -1332,7 +1332,7 @@ rte_eal_init(int argc, char **argv)
> }
>
> eal_mcfg_complete();
> -
> + rte_log(RTE_LOG_DEBUG, RTE_LOGTYPE_EAL, "DPDK version: %s\n", rte_version());
> return fctret;
> }
>
> diff --git a/lib/eal/windows/eal.c b/lib/eal/windows/eal.c
> index 3d8c520412..5e6d5d8930 100644
> --- a/lib/eal/windows/eal.c
> +++ b/lib/eal/windows/eal.c
> @@ -419,6 +419,7 @@ rte_eal_init(int argc, char **argv)
> */
> rte_eal_mp_remote_launch(sync_func, NULL, SKIP_MAIN);
> rte_eal_mp_wait_lcore();
> + rte_log(RTE_LOG_DEBUG, RTE_LOGTYPE_EAL, "DPDK version: %s\n", rte_version());
> return fctret;
> }
>
NAK
DPDK is already too chatty at startup.
If your application needs it then do-it-yourself.
next prev parent reply other threads:[~2021-09-01 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 6:18 Aman Singh
2021-09-01 6:55 ` Andrew Rybchenko
2021-09-01 9:14 ` Bruce Richardson
2021-09-02 10:02 ` Ferruh Yigit
2021-09-01 17:12 ` Stephen Hemminger [this message]
2021-09-02 10:11 ` Ferruh Yigit
2021-09-02 10:27 ` Bruce Richardson
2021-09-06 13:28 ` Singh, Aman Deep
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=20210901101253.6991a2f6@hermes.local \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=dev@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).