DPDK usage discussions
 help / color / mirror / Atom feed
From: "Lukáš Šišmiš" <sismis@cesnet.cz>
To: users@dpdk.org
Subject: Wrapping DPDK log messages with an application logger
Date: Thu, 22 Jun 2023 17:45:38 +0200	[thread overview]
Message-ID: <8575de3e-d63f-f4c6-dd15-92e576c622f6@cesnet.cz> (raw)

Hi all,


I would like to ask you if you know of a way how could I wrap log 
messages coming from the DPDK by an application logger so that output of 
the application is unified. I would think there could be opportunity to 
pass my logging callback into DPDK but I have not found it. The only 
thing that I found was setting the stream (rte_openlog_stream()). So I 
think I could use a Linux pipe to which DPDK would write to and the 
application would read the contents of it, parsing it into messages and 
logging it with the application logger. The proposed solution is 
described in this ticket: 
https://redmine.openinfosecfoundation.org/issues/6114

Is there any alternative solution?

To provide an example of what I am talking about, currently the 
application output is as follows:

"""
Config: affinity: Found affinity definition for "worker-cpu-set" 
[AffinitySetupLoadFromConfig:util-affinity.c:201]
Config: affinity: Using default prio 'medium' for set 'worker-cpu-set' 
[AffinitySetupLoadFromConfig:util-affinity.c:249] <- colored log from 
Suricata
EAL: No free 2048 kB hugepages reported on node 0 <- DPDK log

"""

Here is an example of the ideal output:

"""

Config: affinity: Found affinity definition for "worker-cpu-set" 
[AffinitySetupLoadFromConfig:util-affinity.c:201]
Config: affinity: Using default prio 'medium' for set 'worker-cpu-set' 
[AffinitySetupLoadFromConfig:util-affinity.c:249] <- colored log from 
Suricata
Info: EAL: No free 2048 kB hugepages reported on node 0 <- also colored 
log from Suricata

"""

Thank you in advance.


Cheers,
Lukas


             reply	other threads:[~2023-06-22 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22 15:45 Lukáš Šišmiš [this message]
2023-06-22 16:08 ` Dmitry Kozlyuk
2023-06-25 14:51   ` Stephen Hemminger

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=8575de3e-d63f-f4c6-dd15-92e576c622f6@cesnet.cz \
    --to=sismis@cesnet.cz \
    --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).