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 56AC3A0503 for ; Fri, 6 May 2022 16:55:33 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E4F8440395; Fri, 6 May 2022 16:55:32 +0200 (CEST) Received: from mail-pl1-f173.google.com (mail-pl1-f173.google.com [209.85.214.173]) by mails.dpdk.org (Postfix) with ESMTP id 313244014F for ; Fri, 6 May 2022 16:55:31 +0200 (CEST) Received: by mail-pl1-f173.google.com with SMTP id i17so7661713pla.10 for ; Fri, 06 May 2022 07:55:30 -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=dvZsWD46wq3aktHTJBVFsDG7tYbqNmBRx9X8IRP2yTg=; b=PCqew7Kx5PnUUp/IhcB5+QfEcM+hkyv6cdM+4cqMFDBPl2J/jfXoiQt+etOhc5wmMq +K72c4AxCyPfXILvIGwVsb+pcN72iUnqy6TzLPPJJIdw1qVBzZkH89vigfqdwnESCgH4 TjqvgahglbeR/f9nnzR8wkwhjf2LrSoHjfG4u0554mZDlmR01d6rk/135CpPVjIJtIOt zQlN/0Xzwpf3CvN6CD07GnfxvD1oVCUmESK6eus/qNSa9rzWbQ/ZwB/GM+vtSaX2qlX/ H8Oz32iTDR7LWhoNfDUBK9SDmEVgjo4fcCb+MbsWjF9ag+4dDMIYWzMUIc8ubBNcuP48 ZYVA== 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=dvZsWD46wq3aktHTJBVFsDG7tYbqNmBRx9X8IRP2yTg=; b=0VoTgBiIrhxzGb7YlzFYLllc67u0i+bTeJapg+/DViQE8nvMKC4VZF+iUriQ2YgJOk nwsBZjnW0E71M7FTV5i7ezYOmT+NjJe2xDqoxlmfQBjFui/nVJEZ/OHJJJCwY897nZzD uk61YkoxjhFN7LqAxXwQs8+jW7iRJv0UUJ6Mq/ROXTPGBFNibWTqUqsereJ3FbNpBZ2F CsVKPNCNiG1HW39XANRYGB3HGXKtdQCT3K1tvaELCK16wKwus84vxN+LuGyd6t+qD2In fsV5FbtZKXL6Rln2eLxC/UIkGIsYxwCbcUY7iDP/OrsUTGwv3pThN5q1hUP2xBqQ+5P1 avyQ== X-Gm-Message-State: AOAM533p22ruJre3c/yOia7CbwW2RANnq8xP7IQgq8rY+BK3T+xb2JeX RK3F/wvjiAHasDBNCL1KxAp8dUF8lB+xLA== X-Google-Smtp-Source: ABdhPJzWIcIc3Xqft0HxYwaxH0t/h664KTN5YZYbRea7S01rtPxNkY+v2PAdyk+9k19FGGVWmG6RAA== X-Received: by 2002:a17:90b:78b:b0:1d9:6cd6:3f4c with SMTP id l11-20020a17090b078b00b001d96cd63f4cmr12667346pjz.240.1651848930072; Fri, 06 May 2022 07:55:30 -0700 (PDT) Received: from hermes.local (204-195-112-199.wavecable.com. [204.195.112.199]) by smtp.gmail.com with ESMTPSA id l19-20020a170902e2d300b0015e8d4eb1edsm1802216plc.55.2022.05.06.07.55.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 06 May 2022 07:55:29 -0700 (PDT) Date: Fri, 6 May 2022 07:55:27 -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: <20220506075527.2acefd5a@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 > > > The timestamp for packet capture in DPDK is done when packet is queued to the device. It is not possible with current driver architecture to get timestamp when/after the packet was transmitted.