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 E0A83A04B1 for ; Wed, 19 Jan 2022 17:37:34 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6C08B4116D; Wed, 19 Jan 2022 17:37:34 +0100 (CET) Received: from mail-pj1-f45.google.com (mail-pj1-f45.google.com [209.85.216.45]) by mails.dpdk.org (Postfix) with ESMTP id AA7FE41147 for ; Wed, 19 Jan 2022 17:37:33 +0100 (CET) Received: by mail-pj1-f45.google.com with SMTP id a1-20020a17090a688100b001b3fd52338eso3125123pjd.1 for ; Wed, 19 Jan 2022 08:37:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=dXEKpVErxGwS7UjNVwHiMpgC6ylw5KFEOUU9tDNosyY=; b=28D7vo9S8t+yFWBflQe8v8mjopNYId/58ulSbZ5iH0Nv8MnujQu5MP2Nu3MsLGrjYq edxJEYQYDtN6FXjFAS9mUR7Ecwha53eHv8QVqeFsgxyKBgvpGgnkehOcMVH7W6RGgmHf VcY7KCyNiTXEWgJgePCBw6GHrnIRbKOiH0Gg1cS2iS3nBdLt7xrTc7IdYZ94h30ENFCx MK7YEpxhGj4bTJnkonNUl0ETDRbPEsH2mhKtCsNMWPyIM9ST2+UY+HlTn6KB1j5fytsy 24IpErWKJTqwGO9jaqlabaPuwAzNezdzlZYGYo47n3fIDeqlaY5Oa9PXcAtl0ox9OYIv pYTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=dXEKpVErxGwS7UjNVwHiMpgC6ylw5KFEOUU9tDNosyY=; b=rM1CtB0n4lJzD++rw3YgXTqghXB3iuJkn3XlTZFm2VVfhz60YijXAg2SD/3MT5dQk1 Dne2P7Y+D8vy5wEjc1BslQJHb1R4kcaIKG+QxpzJbHS5/dQlbT8DzUz+qSY3KUIJjul2 E/1uw+g9nsxGtL72QGcrO3eYbtCRGT4eCDxgf0QPcbx6O+j2VSRZG3+Vg75Z2hPYL1/F jXSrcgLfDgdU7jvsomItonLQLY5dU6t4jJteUPs7xMhf4goBR0ZM5ezKvnJ30xvNhc/q n/djQviyqox5a6KGygutIMsHbiomoKT2dUAc2oPVXySng4Xkuxh0yxTyo1DxMCJep+hA gupg== X-Gm-Message-State: AOAM532V+h3pKRjFyn34GhZzi70DGne5lncRkxkRnoCPsZCE4YoV7gB+ 42bJKmb+cmdLRY0G5oGvClLnzw== X-Google-Smtp-Source: ABdhPJxf/6GnKiPKt4s84JHlroVU9ZwgMk0UlGPHEIdKpJ97g6d5szj+UmOZwA2uEGnGa4O+jRBNFg== X-Received: by 2002:a17:902:ea0f:b0:14a:8e80:cc96 with SMTP id s15-20020a170902ea0f00b0014a8e80cc96mr26635907plg.70.1642610252646; Wed, 19 Jan 2022 08:37:32 -0800 (PST) Received: from hermes.local (204-195-112-199.wavecable.com. [204.195.112.199]) by smtp.gmail.com with ESMTPSA id p2sm232304pgb.25.2022.01.19.08.37.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 19 Jan 2022 08:37:32 -0800 (PST) Date: Wed, 19 Jan 2022 08:37:29 -0800 From: Stephen Hemminger To: Jon Ross Cc: users@dpdk.org Subject: Re: how to enable lib_pdump? Message-ID: <20220119083729.48d9732b@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Tue, 18 Jan 2022 10:42:16 -0800 Jon Ross wrote: > dpdk-dumpcap works fine w/ dpdk-testpmd running, but I can't get it to > work while my app is running. > > The docs say to do it the way testmpd does it. But testpmd does... > everything? It's hard to tell what's needed to get capture working. > You need at a minimum: 1. primary/secondary process support 2. ethedev rx/tx callbacks enabled 3. rte_pdump_init() called in primary 4. enough shared memory (huge pages) for additional copies. > The only reference to anything related to lib_pdump in testpmd is the > call to rte_pdump_init(). But adding this call seems to have no > effect. > > Just to make sure "it's not me" I added the call to the > examples/skeleton app, and dpdk-dumpcap will not run w/ the modified > sample app. So it seems like it's more than just calling > rte_pdump_init(). Can anyone shed some light on what needs to happen > to get an app working w/ dpdk-dumpcap? > > I'm using dpdk version v21.11, compile from source via github. > > Thanks, > -Jon Most failures are because of doing something that breaks primary/secondary process support. Like using --in-memory or having a device that won't support primary/secondary.