From: Sunny Keshri <sunnykeshri16@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: Logs/trace for dpdk code
Date: Tue, 13 Dec 2022 17:58:08 +0530 [thread overview]
Message-ID: <CAA57-5o-wNMfMM6jizXBPYRtBFD+21XYhJ0=F=h7MeCjS9C4sw@mail.gmail.com> (raw)
In-Reply-To: <20221212132514.18475836@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
Thanks Stephen for providing some reference.
Regards,
Sunny
On Tue, Dec 13, 2022, 02:55 Stephen Hemminger <stephen@networkplumber.org>
wrote:
> On Tue, 13 Dec 2022 00:31:49 +0530
> Sunny Keshri <sunnykeshri16@gmail.com> wrote:
>
> > Hi all,
> >
> > Can someone please help me where the logs or trace is being stored? And
> > how to get the logs/traces for dpdk code. Any pointers would be
> appreciated.
> >
> > Thanks & Regards,
> > Sunny
>
> Applications using DPDK log facilities print to stdout and also to syslog.
> Where syslog ends up depends on the OS infrastructure. In most modern Linux
> distro's it ends up being part of systemd's journal.
>
[-- Attachment #2: Type: text/html, Size: 1179 bytes --]
prev parent reply other threads:[~2022-12-13 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 19:01 Sunny Keshri
2022-12-12 21:25 ` Stephen Hemminger
2022-12-13 12:28 ` Sunny Keshri [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='CAA57-5o-wNMfMM6jizXBPYRtBFD+21XYhJ0=F=h7MeCjS9C4sw@mail.gmail.com' \
--to=sunnykeshri16@gmail.com \
--cc=stephen@networkplumber.org \
--cc=users@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).