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 02868431E2 for ; Mon, 23 Oct 2023 17:33:01 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E7B624027E; Mon, 23 Oct 2023 17:33:00 +0200 (CEST) Received: from mail-qv1-f49.google.com (mail-qv1-f49.google.com [209.85.219.49]) by mails.dpdk.org (Postfix) with ESMTP id 2006C40151 for ; Mon, 23 Oct 2023 17:32:59 +0200 (CEST) Received: by mail-qv1-f49.google.com with SMTP id 6a1803df08f44-66d332f23e4so21956486d6.0 for ; Mon, 23 Oct 2023 08:32:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698075178; x=1698679978; darn=dpdk.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=mA5YJx/kCUD4zsFCESACbm1+CEaO8xaeYA3q97YQDeU=; b=XM0JaWrLjstb1iIoHtTDla8cwtUssQxxyxok0BmSeVuubaA0YdHPzgeeL7mSzSpZv6 fhcg3V16Xdh3CO8jLHd/Ht4kOIYf5gTfmYb0AzITNQRLvOMj2Yl+5qOueGJ2W+RtbOWJ 815FvcT8XSuQ5ZYythJMmPVXe3aDYTJzFB2vYLZyb9/uDPXsPPee92fyxUJxFtBPmsBg BnXlWZtai5WePEfxW+jYHg93cdaEU+jGelaeGSF1GwyW+J+7pTJUnSr2yB4lHz+vBKO7 FZaJpUK4pXg/E0qfeFZf0Ef9vR/MCP/EWA5Bl9pV5oXEVYglF5eae6EMMTyR8oQt5LgQ IlUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698075178; x=1698679978; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=mA5YJx/kCUD4zsFCESACbm1+CEaO8xaeYA3q97YQDeU=; b=gOGM4mbW6ab7J+Pt2uTIhdextnq4trFCDYFiyNyfRUFyOqxDlSca1XWohJmVQeNFhD 2hezrqRbPNn8+OHwfLHWa+mFzLXCHGh5USWtY9WXd339OnjX4XJXN+LU7xJPHgdJu0gQ H/bItzGFE+onajG8zxvjTC/akQRl/batQKN11HP1Kbdib36XJLKFek1SH0JEE8rmhTUs ZkajN//VMYyW89S6wPsH9T05XP6e5dCvPMftS+JfNRgG8sVZinf/C/fvcfG1VdsGgYlM BkpDjoGOveL7dXMWRV99KsqHqOsI4x9/KMd7K3S0g9QYHrGkJ56uFevljBTnAAmyhsYZ lAUg== X-Gm-Message-State: AOJu0YzGazL7kFXRjoOcBzvTbB0AHXx43MmRWUku1GqdqhMNP0VAtBEz BYsdRObiRwhhaDQwH/jYUGRD2bgo9oFeJo4gGUmJ/4hQqBh7iw== X-Google-Smtp-Source: AGHT+IEtvXYajOzyLea0mgEU6kRvxo05bTN3Fo2LA48vRbTm/6fH2/0qGjqnKRHhrOqhgBUZnYmybfQrXlFX7UfIFes= X-Received: by 2002:ad4:5c8d:0:b0:64c:9d23:8f55 with SMTP id o13-20020ad45c8d000000b0064c9d238f55mr13542882qvh.58.1698075178306; Mon, 23 Oct 2023 08:32:58 -0700 (PDT) MIME-Version: 1.0 From: Pavel Vazharov Date: Mon, 23 Oct 2023 18:32:48 +0300 Message-ID: Subject: Questions about the the pdump functionality To: users Content-Type: multipart/alternative; boundary="000000000000ce1179060863efd4" 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 --000000000000ce1179060863efd4 Content-Type: text/plain; charset="UTF-8" Hi there, We've a DPDK based application from which we need to take packet dumps from time to time when problems arise. We are planning to use librte_pdump functions and the dpdk-dumppcap tool. I've few questions in related to the pdump functionality which we want to use: - Is calling `rte_pdump_init` at the startup of the main application causing some overhead for the packet processing during its run if there is no actual packet capturing enabled by the dpdk-dumppcap tool? I suppose there should be some check in place but is it something like a single `if` condition on a boolean flag or something heavier? - Is it possible then to call `rte_pdump_init` during the runtime of the main application only when I know that I'm about to start the dpdk-dumppcap tool? I mean, is it supported and safe to call `rte_pdump_init` and `rte_pdump_uninit` while the main application is running and processing packets or these functions are supposed to be called only at application startup and application stop. Thanks in advance, Pavel. --000000000000ce1179060863efd4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi there,

We= 9;ve a DPDK based application from which we need to take packet dumps from = time to time when problems arise. We are planning to use librte_pdump funct= ions and the dpdk-dumppcap tool.
I've few questions in related to th= e pdump functionality which we want to use:
- Is calling `rte_pdum= p_init` at the startup of the main application causing some overhead for th= e packet processing during its run if there is no actual packet capturing e= nabled by the dpdk-dumppcap tool? I suppose there should be some check in p= lace but is it something like a single `if` condition on a boolean flag or = something heavier?
- Is it possible then to call `rte_pdump_init` = during the runtime of the main application only when I know that I'm ab= out to start the dpdk-dumppcap tool? I mean, is it supported and safe to ca= ll `rte_pdump_init` and `rte_pdump_uninit` while the main application is ru= nning and processing packets or these functions are supposed to be called o= nly at application startup and application stop.

Thanks in a= dvance,
Pavel.
--000000000000ce1179060863efd4--