From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Su, Simei" <simei.su@intel.com>, "Yang, Qiming" <qiming.yang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Wu, Wenjun1" <wenjun1.wu@intel.com>
Subject: RE: [PATCH v3 0/3] net/iavf: support Rx timestamp on flex descriptor
Date: Fri, 29 Apr 2022 02:56:50 +0000 [thread overview]
Message-ID: <a8d279c155664e548d0e27a6d6a7da6e@intel.com> (raw)
In-Reply-To: <20220428081346.94049-1-simei.su@intel.com>
> -----Original Message-----
> From: Su, Simei <simei.su@intel.com>
> Sent: Thursday, April 28, 2022 4:14 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Yang, Qiming <qiming.yang@intel.com>
> Cc: dev@dpdk.org; Wu, Wenjun1 <wenjun1.wu@intel.com>; Su, Simei
> <simei.su@intel.com>
> Subject: [PATCH v3 0/3] net/iavf: support Rx timestamp on flex descriptor
>
> [PATCH v3 1/3] add related ops and structure for Rx timestamp in virtual
> channel.
> [PATCH v3 2/3] add support for Rx timestamp on flex descriptor in driver.
> [PATCH v3 3/3] improve performance with Rx timestamp enabled.
>
> v3:
> * Rebase code.
> * Fix compile warning.
>
> v2:
> * Add release notes and doc update.
>
> Simei Su (3):
> common/iavf: support Rx timestamp in virtual channel
> net/iavf: enable Rx timestamp on Flex Descriptor
> net/iavf: improve performance of Rx timestamp offload
>
> doc/guides/nics/features/iavf.ini | 1 +
> doc/guides/rel_notes/release_22_07.rst | 2 +-
> drivers/common/iavf/virtchnl.h | 62 +++++++++++++++++++++++-
> drivers/net/iavf/iavf.h | 6 +++
> drivers/net/iavf/iavf_ethdev.c | 35 ++++++++++++++
> drivers/net/iavf/iavf_rxtx.c | 74 +++++++++++++++++++++++++++++
> drivers/net/iavf/iavf_rxtx.h | 21 +++++++++
> drivers/net/iavf/iavf_rxtx_vec_common.h | 3 ++
> drivers/net/iavf/iavf_vchnl.c | 83 ++++++++++++++++++++++++++++----
> -
> 9 files changed, 273 insertions(+), 14 deletions(-)
>
> --
> 2.9.5
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2022-04-29 2:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 2:13 [PATCH v1 " Simei Su
2022-04-08 2:13 ` [PATCH v1 1/3] common/iavf: support Rx timestamp in virtual channel Simei Su
2022-04-08 2:13 ` [PATCH v1 2/3] net/iavf: enable Rx timestamp on Flex Descriptor Simei Su
2022-04-08 2:13 ` [PATCH v1 3/3] net/iavf: improve performance of Rx timestamp offload Simei Su
2022-04-24 7:08 ` [PATCH v2 0/3] net/iavf: support Rx timestamp on flex descriptor Simei Su
2022-04-24 7:08 ` [PATCH v2 1/3] common/iavf: support Rx timestamp in virtual channel Simei Su
2022-04-24 7:08 ` [PATCH v2 2/3] net/iavf: enable Rx timestamp on Flex Descriptor Simei Su
2022-04-24 7:08 ` [PATCH v2 3/3] net/iavf: improve performance of Rx timestamp offload Simei Su
2022-04-28 8:13 ` [PATCH v3 0/3] net/iavf: support Rx timestamp on flex descriptor Simei Su
2022-04-28 8:13 ` [PATCH v3 1/3] common/iavf: support Rx timestamp in virtual channel Simei Su
2022-04-28 8:13 ` [PATCH v3 2/3] net/iavf: enable Rx timestamp on Flex Descriptor Simei Su
2022-04-28 8:13 ` [PATCH v3 3/3] net/iavf: improve performance of Rx timestamp offload Simei Su
2022-05-10 16:00 ` Thomas Monjalon
2022-04-29 2:56 ` Zhang, Qi Z [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=a8d279c155664e548d0e27a6d6a7da6e@intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=qiming.yang@intel.com \
--cc=simei.su@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).