From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail04.ics.ntt-tx.co.jp (mail05.ics.ntt-tx.co.jp [210.232.35.69]) by dpdk.org (Postfix) with ESMTP id 6E5ED1BD4C for ; Fri, 21 Dec 2018 07:43:51 +0100 (CET) Received: from gwchk03.silk.ntt-tx.co.jp (gwchk03.silk.ntt-tx.co.jp [10.107.0.111]) by mail04.ics.ntt-tx.co.jp (unknown) with ESMTP id wBL6hnq9025926; Fri, 21 Dec 2018 15:43:49 +0900 Received: (from root@localhost) by gwchk03.silk.ntt-tx.co.jp (unknown) id wBL6hnML008892; Fri, 21 Dec 2018 15:43:49 +0900 Received: from gwchk.silk.ntt-tx.co.jp [10.107.0.110] by gwchk03.silk.ntt-tx.co.jp with ESMTP id RAA08890; Fri, 21 Dec 2018 15:43:49 +0900 Received: from imss06.silk.ntt-tx.co.jp (localhost [127.0.0.1]) by ccmail04.silk.ntt-tx.co.jp (unknown) with ESMTP id wBL6hncv014127; Fri, 21 Dec 2018 15:43:49 +0900 Received: from imss06.silk.ntt-tx.co.jp (localhost [127.0.0.1]) by imss06.silk.ntt-tx.co.jp (unknown) with ESMTP id wBL6hnV0001274; Fri, 21 Dec 2018 15:43:49 +0900 Received: from ccmail04 (smtp03.silk.ntt-tx.co.jp [10.107.0.135]) by imss06.silk.ntt-tx.co.jp (unknown) with SMTP id wBL6hnsh001271; Fri, 21 Dec 2018 15:43:49 +0900 Date: Fri, 21 Dec 2018 15:42:12 +0900 From: Hideyuki Yamashita In-Reply-To: <20181220191013.358bebd8@xeon-e3> References: <201812210049.wBL0nPMM001632@ccmail04.silk.ntt-tx.co.jp> <20181220191013.358bebd8@xeon-e3> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.74 [ja] X-CCMail7: CC-Mail-V7.0.2-Client-Relayed Message-Id: <201812210643.wBL6hXX5013986@ccmail04.silk.ntt-tx.co.jp> X-TM-AS-MML: No X-CC-Mail-RelayStamp: CC-Mail-V5.14-Server To: Stephen Hemminger Cc: "users@dpdk.org" Subject: Re: [dpdk-users] How to show debug log in DPDK and DPDK application X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Dec 2018 06:43:52 -0000 > On Fri, 21 Dec 2018 09:48:04 +0900 > Hideyuki Yamashita wrote: > > > Hello > > > > I am a developer for DPDK application(SPP). > > And I have a very basic question how to debug by > > increasing log level. > > > > Q1.Are thre any documents those describe the following? > > - how to output debug log of DPDK > > - how to output debut log of DPDK application > > > > As I did quick search on Google, no official documents found. > > If above is yes. > > Please let me know how to achieve those. > > > > Thanks in advance for your guidance to newbie! > > > > BR, > > Hideyuki Yamashita > > NTT TechnoCross > > > > > > logging in current DPDK is controlled per subsystem. > > See: rte_log_set_level_pattern and rte_set_level > > This can be set on command line or with API. > > The default log output on DPDK is to stdout of the application. > This is not useful for a long running service like a daemon, > but the log can be captured by either opening a file and using: > rte_openlog_stream > > Or also by using glibc stdio function open_memstream to make a memory stream > and pass that. This requires a bit more setup. Hello Stephen, Thaks for your guidance. I will read those. But at a glance, it looks like those are in API documents and I wondered if those are well documented in somewhere in developers guide so that developers like me can easily find the path. What do you think? Thanks! BR, Hideyuki NTT TechnoCross