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 27DCF42923 for ; Wed, 12 Apr 2023 09:05:52 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 09B964111C; Wed, 12 Apr 2023 09:05:49 +0200 (CEST) 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 81EFE40FAE for ; Wed, 12 Apr 2023 09:05:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1681283145; 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=kPHUz3zCvCsP9vfhuRyLBNSSdTrtqvzskzFuXmfhV6M=; b=AsowtOBlMAUWM2r1O8vh4HNaGEkDhVzBzsg6MNI6z6BZCHVU7CZjdGUQiO97e/PEomZk1+ VC1NVsEUaJ3p5J4IvyhqwvhYs5ZmNtoWuMWOjD3/sGB/M2cez3Yckx9KSFne0bmKoD9btf SDV971xn4LJjvYJsanKANWRFPgBiEWg= Received: from mail-pj1-f69.google.com (mail-pj1-f69.google.com [209.85.216.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-127-B_EsiJF1OYGMgMY2RkbdWg-1; Wed, 12 Apr 2023 03:05:44 -0400 X-MC-Unique: B_EsiJF1OYGMgMY2RkbdWg-1 Received: by mail-pj1-f69.google.com with SMTP id q88-20020a17090a17e100b00244b0813a68so4250772pja.9 for ; Wed, 12 Apr 2023 00:05:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681283144; x=1683875144; 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=kPHUz3zCvCsP9vfhuRyLBNSSdTrtqvzskzFuXmfhV6M=; b=BceTbDGa2hEwWh9T41lo8IJB1CxE3zq9Q1ElNm64lM2E1e7JMrK+yFFI99ecr+W9XA /wM5GhKRi6VQHrPOf7/OD2Ug4Kd6T0f2ICCPTPYxfoamgipdIDe25Av6wJqQZDTm+EqD uqDInDmOvM4lUgQbbpA/cVv3QlyBE1PlaqKQ3byMrQY4zPVREnL3NJ05FOtkAiWuBF75 awLBZqeWn7D2a8jULQYX1OwrTFfWIJkkWfK9gbbXNSxJl65Oh4KrP/jkOcGNJON+7R0u sUDxlBcnUIiIUQT77oHYSZQ+AzvS5jfyzu6n/7CUl86XXNpwcB7Q2f65I7UmiBoNNYDs Nj7A== X-Gm-Message-State: AAQBX9dGfY/v9/xfmvOS8f1KyauzdHSjhxHyKHJQ9Gr5Qo+KlM/PdyvN KQcthLq6f09t72TdGSA/tlwVSgvYxmEVmwpEZPHXXFSRDtwO2owAjilliy2FDrzd4o6CDwrNFgk 3wTASqRvXHRvNWew48zFSMg== X-Received: by 2002:a17:902:b78c:b0:1a1:b305:f891 with SMTP id e12-20020a170902b78c00b001a1b305f891mr339441pls.9.1681283143779; Wed, 12 Apr 2023 00:05:43 -0700 (PDT) X-Google-Smtp-Source: AKy350bJ504KTiK7n9jRrBbRMC12yA3yvEEtSh65LTEvGUeQ1mu4pK0NfsosfO3cw1JWiEjL2vqciSpImplITCSKdzY= X-Received: by 2002:a17:902:b78c:b0:1a1:b305:f891 with SMTP id e12-20020a170902b78c00b001a1b305f891mr339434pls.9.1681283143480; Wed, 12 Apr 2023 00:05:43 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 12 Apr 2023 09:05:32 +0200 Message-ID: Subject: Re: Hardware timestamps To: =?UTF-8?B?0JjQs9C+0YDRjCDQmg==?= , Qiming Yang , Wenjun Wu , Igor Russkikh Cc: users@dpdk.org, dev@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 Wed, Apr 12, 2023 at 8:57=E2=80=AFAM =D0=98=D0=B3=D0=BE=D1=80=D1=8C =D0= =9A wrote: > > I have tried to get hw timestamps of packets on Intel X550T(10G) and AQC1= 07(10G). > But RTE_ETH_RX_OFFLOAD_TIMESTAMP =3D 0 in dev_info.rx_offload_capa. > Tell me is it possible to get hw timestamps on these NICs with DPDK? Looking at the doc, and the code, none of those drivers (net/ixgbe, net/atlantic) seem to support this feature. I'll let the maintainers reply on the feasibility. > Which 10G NICs support this option? The documentation from the main repository provides a list of per driver features: https://doc.dpdk.org/guides/nics/overview.html For an already released DPDK, the link becomes https://doc.dpdk.org/guides-/nics/overview.html. Like, for example: https://doc.dpdk.org/guides-22.11/nics/overview.html --=20 David Marchand