From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Ronak Doshi <doshir@vmware.com>, Jochen Behrens <jbehrens@vmware.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3 next 0/7] net/vmxnet3: upgrade to version 7
Date: Wed, 3 May 2023 18:34:52 +0100 [thread overview]
Message-ID: <8b01a48a-71c3-cb43-b845-d6c8d0417049@amd.com> (raw)
In-Reply-To: <20230428071055.362-1-doshir@vmware.com>
On 4/28/2023 8:10 AM, Ronak Doshi wrote:
> vmxnet3 emulation has recently added several new features including
> support for uniform passthrough(UPT). To make UPT work vmxnet3 has
> to be enhanced as per the new specification. This patch series
> extends the vmxnet3 driver to leverage these new features.
>
> Compatibility is maintained using existing vmxnet3 versioning mechanism as
> follows:
> - new features added to vmxnet3 emulation are associated with new vmxnet3
> version viz. vmxnet3 version 7.
> - emulation advertises all the versions it supports to the driver.
> - during initialization, vmxnet3 driver picks the highest version number
> supported by both the emulation and the driver and configures emulation
> to run at that version.
>
> In particular, following changes are introduced:
>
> Patch 1:
> This patch introduces utility macros for vmxnet3 version 7 comparison
> and updates Copyright information.
>
> Patch 2:
> This patch adds new capability registers to fine control enablement of
> individual features based on emulation and passthrough.
>
> Patch 3:
> This patch adds support for large passthrough BAR register.
>
> Patch 4:
> This patch introduces new command to set ring buffer sizes to pass this
> information to the hardware.
>
> Patch 5:
> For better performance, hardware has a requirement to limit number of TSO
> descriptors. This patch adds that support.
>
> Patch 6:
> Avoid updating rxprod register when in UPT for performance reasons.
>
> Patch 7:
> With all vmxnet3 version 7 changes incorporated in the vmxnet3 driver,
> with this patch, the driver can configure emulation to run at vmxnet3
> version 7.
>
> Changes v2->v3:
> - removed reference to old performance document
>
> Changes in v2:
> - modified the title to include "net/"
> - addressed checkpatch complaints and some typo in patch commits
> - removed RTE_ETH_DEV_CAPA_PASS_THRU as it was specific to vmxnet3
> - added new features information in release notes
> - updated feature related information in vmxnet3 driver documentation
>
> Ronak Doshi (7):
> net/vmxnet3: prepare for version 7 changes
> net/vmxnet3: add support for capability registers
> net/vmxnet3: add support for large passthrough BAR register
> net/vmxnet3: add command to set ring buffer sizes
> net/vmxnet3: limit number of TXDs used for TSO packet
> net/vmxnet3: avoid updating rxprod register frequently
> net/vmxnet3: update to version 7
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-05-03 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 7:10 Ronak Doshi
2023-04-28 7:10 ` [PATCH v3 next 1/7] net/vmxnet3: prepare for version 7 changes Ronak Doshi
2023-04-28 7:10 ` [PATCH v3 next 2/7] net/vmxnet3: add support for capability registers Ronak Doshi
2023-04-28 7:10 ` [PATCH v3 next 3/7] net/vmxnet3: add support for large passthrough BAR register Ronak Doshi
2023-04-28 7:10 ` [PATCH v3 next 4/7] net/vmxnet3: add command to set ring buffer sizes Ronak Doshi
2023-04-28 7:10 ` [PATCH v3 next 5/7] net/vmxnet3: limit number of TXDs used for TSO packet Ronak Doshi
2023-04-28 7:10 ` [PATCH v3 next 6/7] net/vmxnet3: avoid updating rxprod register frequently Ronak Doshi
2023-04-28 7:10 ` [PATCH v3 next 7/7] net/vmxnet3: update to version 7 Ronak Doshi
2023-05-03 17:29 ` Ferruh Yigit
2023-05-03 17:34 ` Ferruh Yigit [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=8b01a48a-71c3-cb43-b845-d6c8d0417049@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=doshir@vmware.com \
--cc=jbehrens@vmware.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).