DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Pankaj Gupta <pagupta@vmware.com>, jbehrens@vmware.com
Cc: dev@dpdk.org
Subject: Re: [PATCH v6 6/9] net/vmxnet3: add version 6 support
Date: Wed, 25 May 2022 11:45:58 +0300	[thread overview]
Message-ID: <cb0e5c60-d10e-61f2-8cfe-c82303cdac6d@oktetlabs.ru> (raw)
In-Reply-To: <20220525004028.24938-7-pagupta@vmware.com>

Hi, Pankaj,

On 5/25/22 03:40, Pankaj Gupta wrote:
> VMXNET3 version 6 supports some new features, including but not limited to:
> - Increased max MTU up to 9190
> - Increased max number of queues, both for Rx and Tx
> - Removes power-of-two limitations
> - Extended interrupt structures, required implementation for
>     additional number of queues
> 
> Tested, using testpmd, for different hardware versions on ESXi 7.0
> Update 2.
> 
> Signed-off-by: Pankaj Gupta <pagupta@vmware.com>
> Reviewed-by: Jochen Behrens <jbehrens@vmware.com>
> ---
>   doc/guides/rel_notes/release_21_08.rst  |   8 +
>   drivers/net/vmxnet3/base/vmxnet3_defs.h |  73 ++++++--
>   drivers/net/vmxnet3/vmxnet3_ethdev.c    | 220 +++++++++++++++++-------
>   drivers/net/vmxnet3/vmxnet3_ethdev.h    |  10 +-
>   drivers/net/vmxnet3/vmxnet3_rxtx.c      |   2 +-
>   5 files changed, 234 insertions(+), 79 deletions(-)
> 
> diff --git a/doc/guides/rel_notes/release_21_08.rst b/doc/guides/rel_notes/release_21_08.rst
> index 4027bd4390..810da2cc1f 100644
> --- a/doc/guides/rel_notes/release_21_08.rst
> +++ b/doc/guides/rel_notes/release_21_08.rst
> @@ -133,6 +133,14 @@ New Features
>   
>   * **Added RETA query and RETA update support for vmxnet3.**
>   
> +* **Added vmxnet3 version 6 supports with some new features.**
> +
> +  * Increased max MTU up to 9190
> +  * Increased max number of queues, both for Rx and Tx
> +  * Removes power-of-two limitations
> +  * Extended interrupt structures, required implementation for additional number
> +of queues
> +

I've realized that I don't understand the last bullet. Could
you clarify it, please, and I'll update it on applying.

Also, JFYI, you should update release notes for 22.07 release, not old 
release notes for 21.08. Don't worry about it now -
I'll move and rephrase it on applying.

Thanks,
Andrew.

  reply	other threads:[~2022-05-25  8:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25  0:40 [PATCH v6 0/9] net/vmxnet3: support versions 5 and 6 Pankaj Gupta
2022-05-25  0:40 ` [PATCH v6 1/9] net/vmxnet3: add version 5 support Pankaj Gupta
2022-05-25  0:40 ` [PATCH v6 2/9] net/vmxnet3: implement RETA query and RETA update Pankaj Gupta
2022-05-25  0:40 ` [PATCH v6 3/9] net/vmxnet3: add Rx queue usage count utility Pankaj Gupta
2022-05-25  0:40 ` [PATCH v6 4/9] net/vmxnet3: fix ethdev callbacks init order Pankaj Gupta
2022-05-25  0:40 ` [PATCH v6 5/9] net/vmxnet3: report HW version on FW version get Pankaj Gupta
2022-05-25  0:40 ` [PATCH v6 6/9] net/vmxnet3: add version 6 support Pankaj Gupta
2022-05-25  8:45   ` Andrew Rybchenko [this message]
2022-05-25 17:13     ` Pankaj Gupta
2022-05-31 12:54       ` Andrew Rybchenko
2022-05-25  0:40 ` [PATCH v6 7/9] net/vmxnet3: advertise RETA size in device info Pankaj Gupta
2022-05-25  0:40 ` [PATCH v6 8/9] net/vmxnet3: set packet type for fragmented packet Pankaj Gupta
2022-05-25  0:40 ` [PATCH v6 9/9] net/vmxnet3: fix merge error in Rx data ring initialization Pankaj Gupta
2022-05-31 13:40 ` [PATCH v6 0/9] net/vmxnet3: support versions 5 and 6 Andrew Rybchenko
2022-05-31 13:41   ` Andrew Rybchenko
  -- strict thread matches above, loose matches on Subject: below --
2022-05-03  4:22 [PATCH 0/8] vmxnet3 version V5 and V6 Pankaj Gupta
2022-05-19  8:04 ` [PATCH v6 0/9] net/vmxnet3: support versions 5 and 6 Andrew Rybchenko
2022-05-19  8:04   ` [PATCH v6 6/9] net/vmxnet3: add version 6 support Andrew Rybchenko

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=cb0e5c60-d10e-61f2-8cfe-c82303cdac6d@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=jbehrens@vmware.com \
    --cc=pagupta@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).