From: Simei Su <simei.su@intel.com>
To: qi.z.zhang@intel.com, junfeng.guo@intel.com
Cc: dev@dpdk.org, wenjun1.wu@intel.com, Simei Su <simei.su@intel.com>
Subject: [PATCH 0/2] net/igc: support Tx timestamp offload
Date: Tue, 20 Dec 2022 11:47:39 +0800 [thread overview]
Message-ID: <20221220034741.447037-1-simei.su@intel.com> (raw)
[PATCH 1/2] add related definitions to support Tx timestamp offload.
[PATCH 2/2] enable Tx timestamp offload by "Launch Time".
Simei Su (2):
net/igc/base: support Tx timestamp offload
net/igc: enable Tx timestamp offload
drivers/net/igc/base/igc_defines.h | 9 +++++
drivers/net/igc/base/igc_regs.h | 8 +++++
drivers/net/igc/igc_ethdev.c | 70 ++++++++++++++++++++++++++++++++++++++
drivers/net/igc/igc_ethdev.h | 6 +++-
drivers/net/igc/igc_txrx.c | 58 ++++++++++++++++++++++++++-----
drivers/net/igc/igc_txrx.h | 3 ++
6 files changed, 145 insertions(+), 9 deletions(-)
--
2.9.5
next reply other threads:[~2022-12-20 3:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 3:47 Simei Su [this message]
2022-12-20 3:47 ` [PATCH 1/2] net/igc/base: " Simei Su
2022-12-20 3:47 ` [PATCH 2/2] net/igc: enable " Simei Su
2023-02-01 7:30 ` [PATCH v2 0/2] net/igc: support launch time offloading Simei Su
2023-02-01 7:30 ` [PATCH v2 1/2] net/igc/base: expose packet pacing registers Simei Su
2023-02-01 7:30 ` [PATCH v2 2/2] net/igc: enable launch time offloading Simei Su
2023-02-01 8:34 ` Zhang, Qi Z
2023-02-01 8:46 ` [PATCH v2 0/2] net/igc: support " Morten Brørup
2023-02-02 7:17 ` [PATCH v3 " Simei Su
2023-02-02 7:18 ` [PATCH v3 1/2] net/igc/base: expose packet pacing registers Simei Su
2023-02-02 7:18 ` [PATCH v3 2/2] net/igc: enable launch time offloading Simei Su
2023-02-03 0:30 ` Stephen Hemminger
2023-02-03 3:22 ` Su, Simei
2023-02-02 8:46 ` [PATCH v3 0/2] net/igc: support " Zhang, Qi Z
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=20221220034741.447037-1-simei.su@intel.com \
--to=simei.su@intel.com \
--cc=dev@dpdk.org \
--cc=junfeng.guo@intel.com \
--cc=qi.z.zhang@intel.com \
--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).