From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] How to use ixgbe module log?
Date: Thu, 28 Sep 2017 12:54:04 +0100 [thread overview]
Message-ID: <a0f06c3e-2408-f478-1ec2-2b5e29f5eb95@intel.com> (raw)
In-Reply-To: <CAOE=1Z2C3qaf-0_bgM5Ea-kuSOz9Bv3EQ8c1FH=hnWtu7p+EYg@mail.gmail.com>
On 28-Sep-17 11:26 AM, Sam wrote:
> Hi all,
>
> I'm working on ixgbe, I want to enable "PMD_RX_LOG" and "PMD_TX_LOG", how
> to do this?
>
> As for normal application, I could use --log-level param to start, but
> ixgbe is kernel module, how to do this?
>
> Thank you~
>
Hi Sam,
In DPDK, ixgbe is not a kernel module - these are customized, userspace
drivers. In order to enable RX and TX logging, corresponding config
options should be set at compile time. For example, if you want to
enable RX/TX logging for IXGBE driver, here's a rough list of steps you
need to do:
1) create a custom config file in config/ directory. Copy whatever it is
that you're using for your application (e.g.
defconfig_x86_64-native-linuxapp-gcc), and name it something starting
with defconfig_ (e.g. defconfig_myconfig)
2) Set CONFIG_RTE_LIBRTE_IXGBE_DEBUG_RX and
CONFIG_RTE_LIBRTE_IXGBE_DEBUG_TX (and whatever other options you may
need, see [1] and [2]) to "y" in your custom config
3) do "make config T=myconfig && make" (or whatever other command you
use to build/install DPDK - make sure to specify your custom config as
target)
After that, you should be able to see RX/TX logs in DPDK applications.
[1] http://dpdk.org/browse/dpdk/tree/config/common_base#n171
[2] http://dpdk.org/browse/dpdk/tree/drivers/net/ixgbe/ixgbe_logs.h
--
Thanks,
Anatoly
next prev parent reply other threads:[~2017-09-28 11:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 10:26 Sam
2017-09-28 11:54 ` Burakov, Anatoly [this message]
2017-09-29 1:42 ` Sam
2017-09-29 8:38 ` Burakov, Anatoly
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=a0f06c3e-2408-f478-1ec2-2b5e29f5eb95@intel.com \
--to=anatoly.burakov@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).