DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Игорь К" <dzenmaster@gmail.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Qiming Yang <qiming.yang@intel.com>,
	Wenjun Wu <wenjun1.wu@intel.com>,
	 Igor Russkikh <irusskikh@marvell.com>,
	users@dpdk.org, dev@dpdk.org
Subject: Re: Hardware timestamps
Date: Thu, 11 May 2023 23:19:34 +0300	[thread overview]
Message-ID: <CANRAKRX2fwLDmY98t2W=4wXxL4RXfs2CAAJt6pPQV0xRhO74jQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8y50z_TSSvk0FWWKpp8_Dyz9roM17W1BO3Lkpgw8-z=5A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

Thank you for the answer.

ср, 12 апр. 2023 г. в 10:05, David Marchand <david.marchand@redhat.com>:

> Hello,
>
> On Wed, Apr 12, 2023 at 8:57 AM Игорь К <dzenmaster@gmail.com> wrote:
> >
> > I have tried to get hw timestamps of packets on Intel X550T(10G) and
> AQC107(10G).
> > But RTE_ETH_RX_OFFLOAD_TIMESTAMP = 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-<version>/nics/overview.html.
> Like, for example: https://doc.dpdk.org/guides-22.11/nics/overview.html
>
>
> --
> David Marchand
>
>

[-- Attachment #2: Type: text/html, Size: 1741 bytes --]

      reply	other threads:[~2023-05-12 12:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 16:12 Игорь К
2023-04-12  7:05 ` David Marchand
2023-05-11 20:19   ` Игорь К [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANRAKRX2fwLDmY98t2W=4wXxL4RXfs2CAAJt6pPQV0xRhO74jQ@mail.gmail.com' \
    --to=dzenmaster@gmail.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=irusskikh@marvell.com \
    --cc=qiming.yang@intel.com \
    --cc=users@dpdk.org \
    --cc=wenjun1.wu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).