DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shrikrishna Khare <skhare@vmware.com>, yongwang@vmware.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/7] vmxnet3: upgrade to version 3
Date: Fri, 3 Mar 2017 10:57:32 +0000	[thread overview]
Message-ID: <8019d737-e839-b5e9-53ef-3717db6ab5b3@intel.com> (raw)
In-Reply-To: <1488059989-6930-1-git-send-email-skhare@vmware.com>

On 2/25/2017 9:59 PM, Shrikrishna Khare wrote:
> vmxnet3 emulation has recently added several new features which includes
> support for new commands the driver can issue to emulation, change in
> descriptor fields etc. 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 3.
>  - 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:
>   Trivial cleanup in preparation of version 3 changes.
> 
> Patch 2:
>   This patch introduces generalized command interface which allows
>   for easily adding new commands that vmxnet3 driver can issue to the
>   emulation. Further patches in this series make use of this facility.
> 
> Patch 3:
>   Transmit data ring buffer is used to copy packet headers or small
>   packets. It is a fixed size buffer. This patch extends the driver to
>   allow variable sized transmit data ring buffer.
> 
> Patch 4:
>   This patch introduces receive data ring buffer - a set of small sized
>   buffers that are always mapped by the emulation. This avoids memory
>   mapping/unmapping overhead for small packets.
> 
> Patch 5:
>   This patch adds reserved commands.
> 
> Patch 6:
>   In vmxnet3 version 3, the emulation added support for the vmxnet3 driver
>   to communicate information about the memory regions the driver will use
>   for rx/tx buffers. This patch exposes related commands to the driver. The
>   driver is also extended to make use of this feaeture.
> 
> Patch 7:
>   With all vmxnet3 version 3 changes incorporated in the vmxnet3 driver,
>   with this patch, the driver can configure emulation to run at vmxnet3
>   version 3.
> 
> Shrikrishna Khare (7):
>   vmxnet3: prepare for version 3 changes
>   vmxnet3: introduce generalized command interface to configure the
>     device
>   vmxnet3: allow variable length transmit data ring buffer
>   vmxnet3: add receive data ring support
>   vmxnet3: add reserved version 3 command
>   vmxnet3: introduce command to register memory region
>   vmxnet3: update to version 3

Hi Shrikrishna,

Can you please update release notes with this change with one or two
sentences in next version of the patchset?

Also there are helper scripts in dpdk:
- dpdk/devtools/check-git-log.sh to check patch titles
- dpdk/devtools/checkpatches.sh (a wrapper to Linux checkpatch.pl)

Both are generating some warnings, can you please check them?

For checkpatches script, it is free to ignore CAMELCASE &
LONG_LINE_STRING warnings.

Thanks,
ferruh




> 
>  drivers/net/vmxnet3/base/vmxnet3_defs.h |  85 ++++++++++++++++--
>  drivers/net/vmxnet3/vmxnet3_ethdev.c    | 154 +++++++++++++++++++++++++++++++-
>  drivers/net/vmxnet3/vmxnet3_ethdev.h    |  14 +++
>  drivers/net/vmxnet3/vmxnet3_ring.h      |  21 +++++
>  drivers/net/vmxnet3/vmxnet3_rxtx.c      |  45 ++++++++--
>  5 files changed, 304 insertions(+), 15 deletions(-)
> 

  parent reply	other threads:[~2017-03-03 10:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25 21:59 Shrikrishna Khare
2017-02-25 21:59 ` [dpdk-dev] [PATCH 1/7] vmxnet3: prepare for version 3 changes Shrikrishna Khare
2017-02-25 21:59 ` [dpdk-dev] [PATCH 2/7] vmxnet3: introduce generalized command interface to configure the device Shrikrishna Khare
2017-02-25 21:59 ` [dpdk-dev] [PATCH 3/7] vmxnet3: allow variable length transmit data ring buffer Shrikrishna Khare
2017-02-25 21:59 ` [dpdk-dev] [PATCH 4/7] vmxnet3: add receive data ring support Shrikrishna Khare
2017-02-25 21:59 ` [dpdk-dev] [PATCH 5/7] vmxnet3: add reserved version 3 command Shrikrishna Khare
2017-02-25 21:59 ` [dpdk-dev] [PATCH 6/7] vmxnet3: introduce command to register memory region Shrikrishna Khare
2017-03-03 10:46   ` Ferruh Yigit
2017-03-03 10:51   ` Ferruh Yigit
2017-02-25 21:59 ` [dpdk-dev] [PATCH 7/7] vmxnet3: update to version 3 Shrikrishna Khare
2017-03-03 10:57 ` Ferruh Yigit [this message]
2017-03-06 17:25   ` [dpdk-dev] [PATCH 0/7] vmxnet3: upgrade " Shrikrishna Khare
2017-03-07 12:17     ` Ferruh Yigit

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=8019d737-e839-b5e9-53ef-3717db6ab5b3@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=skhare@vmware.com \
    --cc=yongwang@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).