DPDK usage discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: Kilian Holzinger <kilian.holzinger@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Cc: "Guo, Jia" <jia.guo@intel.com>
Subject: Re: [dpdk-users] DPDK e1000 Legacy Transmit Descriptor Format
Date: Thu, 4 Jun 2020 10:03:02 +0000	[thread overview]
Message-ID: <MWHPR11MB1391D8F7EA1E6FF67DBE8212B7890@MWHPR11MB1391.namprd11.prod.outlook.com> (raw)
In-Reply-To: <e8c4e3fe-3ff4-e78f-3e26-666cefc0a7a6@gmail.com>

Hi, Kilian Holzinger
 

> -----Original Message-----
> From: Kilian Holzinger <kilian.holzinger@gmail.com>
> Sent: Wednesday, June 3, 2020 11:21 PM
> To: users@dpdk.org
> Cc: Zhao1, Wei <wei.zhao1@intel.com>; Guo, Jia <jia.guo@intel.com>
> Subject: DPDK e1000 Legacy Transmit Descriptor Format
> 
> Hello,
> 
> today I was trying to find a way to use the Intel LaunchTime feature of the i210
> NIC in conjunction with DPDK IGB PMD driver. I thought it might be easy to get
> it to work, since it might be just some register that is missing. However I
> discovered that the e1000 driver uses the legacy transmit descriptor format
> and therefore the Launch Time feature is not easily available at all in DPDK.

You are righ, it seems igb driver do not get "DMA Time Stamp" at all, although it has use adv descriptor.
 
> Do you see any other options I have to use this feature in DPDK?

No

> Are there plans to move to the new Transmit Descriptor Format?

No plan, You had better enable this field yourself, no need to switch Transmit Descriptor Format, because e1000 it has use adv tx descriptor.

> 
> Best regards
> Kilian Holzinger

  reply	other threads:[~2020-06-04 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 15:21 Kilian Holzinger
2020-06-04 10:03 ` Zhao1, Wei [this message]
2020-06-04 10:10   ` Zhao1, Wei

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=MWHPR11MB1391D8F7EA1E6FF67DBE8212B7890@MWHPR11MB1391.namprd11.prod.outlook.com \
    --to=wei.zhao1@intel.com \
    --cc=jia.guo@intel.com \
    --cc=kilian.holzinger@gmail.com \
    --cc=users@dpdk.org \
    /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).