From: David Marchand <david.marchand@redhat.com>
To: Trey Harrison <harrisondigitalmedia@gmail.com>,
Bruce Richardson <bruce.richardson@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Ian Stokes <ian.stokes@intel.com>
Cc: users@dpdk.org
Subject: Re: Intel 800/700 series support for RTE_ETH_TX_OFFLOAD_SEND_ON_TIMESTAMP?
Date: Mon, 24 Mar 2025 08:33:43 +0100 [thread overview]
Message-ID: <CAJFAV8y=3H0XCDthdCkZomGterHPJ0J8U=RTjfAOZVea32MDmA@mail.gmail.com> (raw)
In-Reply-To: <CAOmq+anRr6a-_EnYBw8X5ELRsER-nAknQ+bFzWdo=kOHQHP_TQ@mail.gmail.com>
On Sat, Mar 22, 2025 at 5:37 AM Trey Harrison
<harrisondigitalmedia@gmail.com> wrote:
>
> It seems that there is no support for
> RTE_ETH_TX_OFFLOAD_SEND_ON_TIMESTAMP on Intel's 700/800 series chips
> in any DPDK release (although, there is support for the 225/226
> chips). I have done as thorough of a search on this as I can, but
> wanted to reach out to actual devs before giving up.
>
> I guess I am hoping to simply confirm, from anyone with knowledge of
> the subject, that there is in fact no such support in any forthcoming
> patches / DPDK releases / driver revisions / etc.
>
> It would also be interesting to know whether the hardware is even
> capable of this feature - if so, maybe it would not be too complicated
> to implement it? Especially since there is an example in net/igc to
> work from..
Adding Intel maintainers in the loop.
--
David Marchand
prev parent reply other threads:[~2025-03-24 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 4:36 Trey Harrison
2025-03-24 7:33 ` David Marchand [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='CAJFAV8y=3H0XCDthdCkZomGterHPJ0J8U=RTjfAOZVea32MDmA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=harrisondigitalmedia@gmail.com \
--cc=ian.stokes@intel.com \
--cc=users@dpdk.org \
--cc=vladimir.medvedkin@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).