From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 7B198A056A;
	Wed, 10 Mar 2021 19:19:30 +0100 (CET)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 3627F22A33E;
	Wed, 10 Mar 2021 19:19:30 +0100 (CET)
Received: from mail-pj1-f52.google.com (mail-pj1-f52.google.com
 [209.85.216.52]) by mails.dpdk.org (Postfix) with ESMTP id 8F08840F35
 for <dev@dpdk.org>; Wed, 10 Mar 2021 19:19:29 +0100 (CET)
Received: by mail-pj1-f52.google.com with SMTP id
 f2-20020a17090a4a82b02900c67bf8dc69so7690590pjh.1
 for <dev@dpdk.org>; Wed, 10 Mar 2021 10:19:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=xco6AiMOyX9GmRcf1coBmbvr5SlX13veWAYOcnNHUPY=;
 b=AS9PQUB2eanQrXlmrxQ5oHttVWljQklsKCE1g9sJT0UJh5cvuLjCC6539eXeSXVMZy
 WytDy6RJmz8a4hDjm9DV7bop9RuOwfBLIEx8Y9y+Q84Ydixe7hLKQoULCek/QWwG7ZWk
 VXflAkrlMuf2BQ/m4EknXFcHpeIDwX4OBwn+dAbQbahBh5ZtbgjJmPFnJ2+XWs0nQ6Da
 T9BQBoS/H5dRmsWlHbqBEoQrI3dq2usVgBs1Ub6Sa4ThoGOGDfTHTIuwbnB3GMFPY9Wk
 EF1MB9byRBihWYR2x0iyPAxpIrGquu2EBCyNtv1iufpcpW/UTtJLglBd2ZiB2yUn3N3R
 ae3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=xco6AiMOyX9GmRcf1coBmbvr5SlX13veWAYOcnNHUPY=;
 b=cKPiNAzsnhrl1RbmTLRwr5MvNToKKpIRLm+dt5YiQcVlEl9LBtKdOudbWqtg14X4+C
 PitGOA4BSo3KJDDQi1WdIM/PBDnIIScoiziaptnVeYWIz+rI9gialaOtmdq+yY4XthNf
 m5FnlcLRqKEttaer4qmE5GvAERr5ovMTg9x4KGm3svizm9IHCzRf9znk44jAhNS/Exe0
 FTy/s95ivOr/A76pgREPLcRGyX/IFznnZX4kWrWVx8glHyWV5sywzGPrM/Ck5rBbZqyv
 he0hObW1wxd1x0A6r+TbMHyAIDSIZLK7zNOydgLWvaUtCXE7uO2axJx8Bdvn5g0O5D0D
 mc1g==
X-Gm-Message-State: AOAM533zlSGvMpjOYScBOf3647HOMPV6p0hetNtPZ6hr+QhhT2iiTixv
 scC0zYuvkZZ/qdREM5kg+gLdz5F8+K99Pyy9X6kdwDb/vUM=
X-Google-Smtp-Source: ABdhPJzYlWsYC1PCrLKyLK0r50D2sjMu+WzJ9T3XT+5I62QTZDQ1XnWYM20u0I4NMkDJdeYLh0PJ54EDjJbMaqFZkYM=
X-Received: by 2002:a17:90b:1950:: with SMTP id
 nk16mr4801545pjb.140.1615400368614; 
 Wed, 10 Mar 2021 10:19:28 -0800 (PST)
MIME-Version: 1.0
References: <CALLOm0PKnw7gDP6aHstwBcJf0_ZSC1wKzE-ei9thVWRNkLHGoQ@mail.gmail.com>
 <20210309122905.46fb344f@hermes.local>
In-Reply-To: <20210309122905.46fb344f@hermes.local>
From: Shanmugasundaram M <shansirtt@gmail.com>
Date: Wed, 10 Mar 2021 23:49:17 +0530
Message-ID: <CALLOm0MnrCOZOsheDvJWPTK1ket8D4SqO8koDB8qeLiNzGDGNw@mail.gmail.com>
To: stephen@networkplumber.org
Cc: dev@dpdk.org
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
Subject: Re: [dpdk-dev] Reg DPDK EAL log-level=8 options is not throwing any
 DEBUG messages in /var/log/messages
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

THanks Steven for the quick response.  I want to enable  EAL module
(complete logging at debug level ) only during bootup of fastpath. Once
bootup is done, i want to move this module log-level to default/ original.
Currently I'm using     --log-level='.*',8  along with
./sources/fp/common/fp-var.h  [ #define FP_LOG_DEFAULT FP_LOG_DEBUG ]
instead of [ #define FP_LOG_DEFAULT FP_LOG_ERR ]. refer below snip
<snip>
-#define FP_LOG_DEFAULT FP_LOG_ERR
+#define FP_LOG_DEFAULT FP_LOG_DEBUG
The problem is its throwing all the other debug messages like this after
fastpath started. Any way to disable below message <snip3> and only log
bootup of EAL debug messages alone ?

REgards,
Shanmugasundaram M

<snip3>
ebug interface eth3 (port 3) is not operative
2021-03-10T18:12:39+00:00 daemon infoblox.localdomain fp-rte[3611]: debug
packet m=0x36575b600 dropped at fp_process_input():178
2021-03-10T18:12:39+00:00 daemon infoblox.localdomain fp-rte[3611]: info
fp_ether_input(ifp=eth1 port=1)
2021-03-10T18:12:39+00:00 daemon infoblox.localdomain fp-rte[3611]: debug
==== mbuf at [0x36866ee80]: 1 segment(s), len=60 port=1
2021-03-10T18:12:39+00:00 daemon infoblox.localdomain fp-rte[3611]: debug
                 next=(nil) shared=0 flags=0x0
2021-03-10T18:12:39+00:00 daemon infoblox.localdomain fp-rte[3611]: debug
    ol flags: 0x0 hash: 0x0
2021-03-10T18:12:39+00:00 daemon infoblox.localdomain fp-rte[3611]: debug
    outer offloads:
2021-03-10T18:12:39+00:00 daemon infoblox.localdomain fp-rte[3611]: debug
        l2: proto ETH hlen 14 flags



On Wed, Mar 10, 2021 at 1:59 AM Stephen Hemminger <
stephen@networkplumber.org> wrote:

> On Wed, 10 Mar 2021 00:30:24 +0530
> Shanmugasundaram M <shansirtt@gmail.com> wrote:
>
> > Dear Team,
> >
> > we are using 18.11.1-6WIND DPDK. we are trying to get EAL Debug messages
> > and we are not able to see any one from them in /var/log/messages. Kindly
> > let me know --log-level=8 is enough or --log-level=*8 is correct  OR
> > --log-level=eal,debug is correct ?
> > Appreciate your quick response.
> >
> > regards,
> > Shanmugasundaram M
>
> DPDK now has log-level on a per-feature level. The old log level was
> global.
> The legacy option is what you are using.
>
> The document is missing about log-level options.
>
> Now log-level takes three forms:
>     --log-level=regex,N
>     --log-level=pattern:N
>     --log-level=N
>
> The first takes a regular expressions so for example:
>      -log-level='pmd\..*,8'
> Would set logging at debug for Poll Mode Drivers.  Regex period
> is match all, not match period.
>
> The second form takes a shell style pattern (glob):
>     --log-level='pmd.net.*:debug'
> Sets debug log level for all Poll Mode Network drivers.
> All forms take numeric or symbolic names for logging levels in current
> versions
>
> The third form sets the global log level only.
>
> The actual logic around what gets logged or not is a union of
> the global and per-logtype argument. So if global log level is
> set high (like NOTICE) then no info or debug messages will get printed.
>
> In other words, --log-level=8 has no effect both because it only
> sets the global level (and the default global level already is 8).
>
> To turn on all logging. Just do --log-level='.*,8' (or similar)
>
>
>
>
>