From: Sam <batmanustc@gmail.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] How to use ixgbe module log?
Date: Fri, 29 Sep 2017 09:42:53 +0800 [thread overview]
Message-ID: <CAOE=1Z32u+A7jKhDjjM1T+GCDt4A_MkzoecGtmk0qY8xsd2MGA@mail.gmail.com> (raw)
In-Reply-To: <a0f06c3e-2408-f478-1ec2-2b5e29f5eb95@intel.com>
My question is not clear. Actually ixgbevf driver in my system is kernel
module, like this:
[root@yf-mos-corp-host175 ~]# modinfo ixgbevf
filename:
/lib/modules/3.10.0-514.10.2.el7.mt20170307.x86_64/kernel/drivers/net/ethernet/intel/ixgbevf/ixgbevf.ko
version: 2.12.1-k-rh7.3
license: GPL
description: Intel(R) 10 Gigabit Virtual Function Network Driver
author: Intel Corporation, <linux.nics@intel.com>
rhelversion: 7.3
srcversion: C9F11E41E5F60ADED5673E1
alias: pci:v00008086d000015A9sv*sd*bc*sc*i*
alias: pci:v00008086d000015A8sv*sd*bc*sc*i*
alias: pci:v00008086d00001564sv*sd*bc*sc*i*
alias: pci:v00008086d00001565sv*sd*bc*sc*i*
alias: pci:v00008086d00001530sv*sd*bc*sc*i*
alias: pci:v00008086d00001515sv*sd*bc*sc*i*
alias: pci:v00008086d0000152Esv*sd*bc*sc*i*
alias: pci:v00008086d000010EDsv*sd*bc*sc*i*
depends:
intree: Y
vermagic: 3.10.0-514.10.2.el7.mt20170307.x86_64 SMP mod_unload
modversions
signer: CentOS Linux kernel signing key
sig_key: 44:C9:F5:E3:67:CB:A0:1D:73:A5:17:C8:70:7B:BA:58:FA:FD:7E:30
sig_hashalgo: sha256
parm: debug:Debug level (0=none,...,16=all) (int)
and I use dpdk_nic_bind with --driver option to bind netdevice with ixgbevf
kernel driver. So I think I use ixgbevf kernel module which is distributed
with kernel, and my kernel is:
3.10.0-514.10.2.el7
2017-09-28 19:54 GMT+08:00 Burakov, Anatoly <anatoly.burakov@intel.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-29 1:42 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
2017-09-29 1:42 ` Sam [this message]
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='CAOE=1Z32u+A7jKhDjjM1T+GCDt4A_MkzoecGtmk0qY8xsd2MGA@mail.gmail.com' \
--to=batmanustc@gmail.com \
--cc=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).