From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C005943C38 for ; Thu, 29 Feb 2024 12:27:00 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 78BE7402BB; Thu, 29 Feb 2024 12:27:00 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id DF064402B4 for ; Thu, 29 Feb 2024 12:26:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1709206018; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=c6oAwgi2ZsmCoibWePaCHvnDF+KIskUL3TA/u4BBeMs=; b=f5ZIvfUh/UvFJIf6jVM2ErDtMVMNBpssUiPgV/gZ16bnPsCkn8Ls2qfGmidjIBa9MMcBby HDUtl4cAh1DLiYczOAiJvGWXsNbuyaNuOzpvwZfs41xwVGBfUkcyXhcEMTiFHiWmMxVr9m GSth5OrnqrcL72aYhZ3kE55obT8dBmg= Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-385-kvsHp5ZYM-eMQHBIXvfTSw-1; Thu, 29 Feb 2024 06:26:57 -0500 X-MC-Unique: kvsHp5ZYM-eMQHBIXvfTSw-1 Received: by mail-lj1-f197.google.com with SMTP id 38308e7fff4ca-2d243193975so5334891fa.2 for ; Thu, 29 Feb 2024 03:26:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709206015; x=1709810815; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=c6oAwgi2ZsmCoibWePaCHvnDF+KIskUL3TA/u4BBeMs=; b=FHRkcwN1XBklBjIU/+krYrv4antDNQkn89KBh0V/qVeTrn6YU9lmSUS/i0idHWl5zP KYYK/tndkiIBWjDr6lVj15IO7BE5kTpumm/G2+2w6N4cIlQdfdP/zvnj4dCIMzrkKAsA XULa07hqVdFqvlPDdy4LfTwW8ZTuJwRp82LecsFAMU8FG6y/aJMOZWAHuolAeFH4jntE 4YAx5vAkdTfuSHeEPCUb9dlQRBw0th4ROObMkcPZWqKGHIv08Dw7VW+ofgxDo9oaKqsn yGaZkvkYo1PJ8la6LWsBCXqiJv308XYFduU/KFsRHy7Sasknogly80lVaDa/sxyuZKUX 5ojA== X-Gm-Message-State: AOJu0YyhX1LDaMsMVU0AR1bbGWs+WYygVvgdPfrUNxjfH1FN2ghLR3gH LaEaKfJL6gjD0zyDUNm2yT4TV3wUiS9bsjgP6IeDbtG+hQBEcRAbkTQV1GEsYB3ulqJ+Ezj+o8m SXvzzy7qAiZ8Zu4iC2ofwEwZzUQxf0MlYTMi1AvGqbBGdoXHPDuFO5NXrtRnnlUZfbKE5XQROqO i0EIgemO6MZWwKawuoWA== X-Received: by 2002:a05:6512:138d:b0:513:2ba9:4b14 with SMTP id fc13-20020a056512138d00b005132ba94b14mr265392lfb.46.1709206015747; Thu, 29 Feb 2024 03:26:55 -0800 (PST) X-Google-Smtp-Source: AGHT+IFOm6s16DJbgdvi5BFG3dv1u3SarFylgOh6hLl9Ar9d3cgwZpgHKKPWIYtESitB4RD1p6C6s0pY11rQg3SrKn8= X-Received: by 2002:a05:6512:138d:b0:513:2ba9:4b14 with SMTP id fc13-20020a056512138d00b005132ba94b14mr265382lfb.46.1709206015396; Thu, 29 Feb 2024 03:26:55 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Thu, 29 Feb 2024 12:26:43 +0100 Message-ID: Subject: Re: How to enable logging and where to find the logs To: Sindhura Bandi Cc: "users@dpdk.org" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Hello, On Thu, Feb 29, 2024 at 9:51=E2=80=AFAM Sindhura Bandi wrote: > > I might be asking a basic question here. I'm facing some issues while bri= nging up a dpdk interface on ovs-dpdk on debian-12. Dpdk version is 22.11.1= . > Dpdk seems to fail to allocate a mempool, even though there seem to be en= ough free huge page memory available on the machine. > Well, this is more a OVS question than a DPDK one :-) There are two things to configure here. > I tried to enable dpdk debugs using the following command, > ovs-vsctl set Open_vSwitch . other_config:dpdk-extra=3D"--log-level=3Dlib= .mbuf:debug" First, as you tried, you must ask DPDK to emit debug logs for the mbuf libr= ary. The above configuration is fine. Just a small note that since OVS 2.14 you can enable logs dynamically without having to restart OVS / setting a dpdk-extra param in ovsdb. For example, I have no dpdk-extra config. # ovs-appctl dpdk/log-list | grep mbuf id 16: lib.mbuf, level is info # ovs-appctl dpdk/log-set lib.mbuf:debug # ovs-appctl dpdk/log-list | grep mbuf id 16: lib.mbuf, level is debug > > The command was accepted, but I don't see any logs from dpdk anywhere in = my /var/log. That is because OVS log framework applies a filter. # ovs-appctl vlog/list | grep dpdk dpdk OFF ERR INFO netdev_dpdk OFF ERR INFO netdev_offload_dpdk OFF ERR INFO The dpdk facility here is only logging ERR level messages to syslog, and INFO level to the /var/log file. You probably want to set: # ovs-appctl vlog/set FILE:dpdk:dbg # ovs-appctl vlog/list | grep dpdk dpdk OFF ERR DBG netdev_dpdk OFF ERR INFO netdev_offload_dpdk OFF ERR INFO Hope that helps. --=20 David Marchand