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 8E896A0503 for ; Fri, 6 May 2022 17:02:10 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 17D214068A; Fri, 6 May 2022 17:02:10 +0200 (CEST) Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) by mails.dpdk.org (Postfix) with ESMTP id 39DAA4014F for ; Fri, 6 May 2022 17:02:09 +0200 (CEST) Received: by mail-pj1-f44.google.com with SMTP id l11-20020a17090a49cb00b001d923a9ca99so7105887pjm.1 for ; Fri, 06 May 2022 08:02:09 -0700 (PDT) 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=OsTsC4GOCBSq+TQo18XnTz0JEpFYeRZtGfufB3OrxAo=; b=P8MDaq1xm7uhNCKYyq8Mm7H8JbbKjS2v6D0ktc33KWAzcQraGDhZqSGC48My+UMrQ1 Xe6jHLePrUPHdffGiOPEhzge+4dMpga9iRpS/pHpoxuSX1vw1piaY6fRsZGE/pOOr3da tzpHdwdwry08+vXF/Cq3bh6zmRWHoBwj06AMuVn401wEKP36wHRySORgsEa/CBiC8hDF W5b8Hm7zpsJ2cFKT6vjKOYveR4VWFp/+I1MuCC1rREH22m45EcV7XCh7o3ppkyo8bBVf SlrY3Pec/04SNNq2mMEZtuALmt35rUgXguSroKeFAUE+j4g8bNRZTe7w9OWqJKhAOOKD OuZA== 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=OsTsC4GOCBSq+TQo18XnTz0JEpFYeRZtGfufB3OrxAo=; b=bNj3nz3sv4nYQz6nlcbhnhXXORjPFehhPL7TTY9B1SvxuQ9Qt4ygXtjHO0qXSg2XNT t2zwsHYU6gnM1itZZ3pIzz6fF42WNSVEEj+09nYmlubSSggj2y9OdJ9YbGTlxgr5/O15 Y7ifTt9h2NS0mgTUGm4eyYFXj3lK9Lvbp/ygsAZ1F2XVkGXsfBDQ8KbzcFEVSb5fagkk GFcNC1WQksO+xb/nNzYQakwImhKBKeF2GGSGGDvdN2kyiVIWJbE+8mVdfRrayuxumbLl G3hhTF1LVchUc2goM2RLQ+p92eoSi51hiDoxOkszlClJvfJO8eUDysdrazGrjJdITecd QpZw== X-Gm-Message-State: AOAM530W2UpiN1IX1YiQnnB5PRBCuyTGUGzETXmmh6ljP98VCiQIyvYY Vf3ixZ2XgseL6NXQDhI1Kd8vaA== X-Google-Smtp-Source: ABdhPJwkEp8vMAauAjvxMy5OwFivapVRstqlhX20TF/i/ZRMKPWfWP81VQ1t7xawgRTLBLddsyuldg== X-Received: by 2002:a17:90b:3b8d:b0:1dc:7637:91c3 with SMTP id pc13-20020a17090b3b8d00b001dc763791c3mr12700440pjb.186.1651849328353; Fri, 06 May 2022 08:02:08 -0700 (PDT) Received: from hermes.local (204-195-112-199.wavecable.com. [204.195.112.199]) by smtp.gmail.com with ESMTPSA id n28-20020a056a000d5c00b0050dc7628148sm3458477pfv.34.2022.05.06.08.02.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 06 May 2022 08:02:07 -0700 (PDT) Date: Fri, 6 May 2022 08:02:06 -0700 From: Stephen Hemminger To: Mikael R Carlsson Cc: "users@dpdk.org" Subject: Re: Configure timestamp source for dpdk-pdump on E810 and DPDK 19.11 Message-ID: <20220506080206.1c9cc5d7@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 Fri, 6 May 2022 07:46:39 +0000 Mikael R Carlsson wrote: > Hi! > > I am using a Intel E810-XXVDA4 and DPDK version 19.11. During troubleshooting we have captures outgoing traffic with dpdk-pdump: > > dpdk-pdump -- --pdump 'port=1,queue=*,tx-dev=/tmp/tx.pcap > > I have opened the pcap-file in wireshark and I can see that some packets are delayed. However, system behavior indicates that the delays I see in the pcap file are not correct, they are too big. My questions is, how is the timestamp on packets in the pcap from dpdk-pdump created, like NIC HW generated, CPU time at disk write etc. or something else? Are there any run-time or build-time options to change the source of the timestamps? > > / Mikael > > > Follow up. The older dump-pdump in 19.11 does timestamps when packet is read from the ring which is bad. You might have better luck with DPDK 20.11 and the dpdk-dumpcap which puts timestamp in when packet is put into ring. Let me give picture: Application (primary) | 1 2 +--+-------------------------> wire | | dumpcap (secondary) +---========--------------> capture file 3 The ==== is ringbuffer between processes 1. Where 20.11 with dpdk-dumpcap gets timestamp 2. Where you want the timestamp but is not possible 3. Where 19.11 and dpdk-pdump gets timestamp