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 next 4/7] vmxnet3: add command to set ring buffer sizes
Date: Wed, 26 Apr 2023 17:58:01 +0100 [thread overview]
Message-ID: <b4b8c6cd-1586-d64c-6ed4-e22fba4dc616@amd.com> (raw)
In-Reply-To: <20230412162636.30843-5-doshir@vmware.com>
On 4/12/2023 5:26 PM, Ronak Doshi wrote:
> This patch adds a new command to set ring buffer sizes. This is
> required to pass the buffer size information to passthrough devices.
> Also, ring sizes are round down to power of 2.
>
> Signed-off-by: Ronak Doshi <doshir@vmware.com>
> Acked-by: Jochen Behrens <jbehrens@vmware.com>
> ---
> drivers/net/vmxnet3/base/vmxnet3_defs.h | 15 +++++++++++++++
> drivers/net/vmxnet3/vmxnet3_ethdev.c | 18 ++++++++++++++++++
> drivers/net/vmxnet3/vmxnet3_ethdev.h | 1 +
> drivers/net/vmxnet3/vmxnet3_rxtx.c | 7 +++++++
> 4 files changed, 41 insertions(+)
>
> diff --git a/drivers/net/vmxnet3/base/vmxnet3_defs.h b/drivers/net/vmxnet3/base/vmxnet3_defs.h
> index 27f35a0062..d8cc295b08 100644
> --- a/drivers/net/vmxnet3/base/vmxnet3_defs.h
> +++ b/drivers/net/vmxnet3/base/vmxnet3_defs.h
> @@ -105,6 +105,9 @@ typedef enum {
> VMXNET3_CMD_RESERVED4,
> VMXNET3_CMD_REGISTER_MEMREGS,
> VMXNET3_CMD_SET_RSS_FIELDS,
> + VMXNET3_CMD_RESERVED9,
> + VMXNET3_CMD_RESERVED10,
> + VMXNET3_CMD_SET_RING_BUFFER_SIZE,
>
> VMXNET3_CMD_FIRST_GET = 0xF00D0000,
> VMXNET3_CMD_GET_QUEUE_STATUS = VMXNET3_CMD_FIRST_GET,
> @@ -822,6 +825,17 @@ typedef enum Vmxnet3_RSSField {
> VMXNET3_RSS_FIELDS_ESPIP6 = 0x0020,
> } Vmxnet3_RSSField;
>
> +typedef
> +#include "vmware_pack_begin.h"
> +struct Vmxnet3_RingBufferSize {
> + __le16 ring1BufSizeType0;
> + __le16 ring1BufSizeType1;
> + __le16 ring2BufSizeType1;
> + __le16 pad;
> +}
> +#include "vmware_pack_end.h"
> +Vmxnet3_RingBufferSize;
> +
As far as I can see these "vmware_pack_begin.h" & "vmware_pack_end.h"
has only file license comment, and I can see this is used in a few other
type declaration.
What is the reasoning behind using these headers?
next prev parent reply other threads:[~2023-04-26 16:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 16:26 [PATCH next 0/7] vmxnet3: upgrade to version 7 Ronak Doshi
2023-04-12 16:26 ` [PATCH next 1/7] vmxnet3: prepare for version 7 changes Ronak Doshi
2023-04-26 16:58 ` Ferruh Yigit
2023-04-12 16:26 ` [PATCH next 2/7] vmxnet3: add support for capability registers Ronak Doshi
2023-04-26 16:55 ` Ferruh Yigit
2023-04-12 16:26 ` [PATCH next 3/7] vmxnet3: add support for large passthrough BAR register Ronak Doshi
2023-04-12 16:26 ` [PATCH next 4/7] vmxnet3: add command to set ring buffer sizes Ronak Doshi
2023-04-26 16:58 ` Ferruh Yigit [this message]
2023-04-26 17:27 ` Ronak Doshi
2023-04-27 8:50 ` Ferruh Yigit
2023-04-27 15:59 ` Ronak Doshi
2023-05-03 10:03 ` Ferruh Yigit
2023-04-12 16:26 ` [PATCH next 5/7] vmxnet3: limit number of TXDs used for TSO packet Ronak Doshi
2023-04-12 16:26 ` [PATCH next 6/7] vmxnet3: avoid updating rxprod register frequently Ronak Doshi
2023-04-12 16:26 ` [PATCH next 7/7] vmxnet3: update to version 7 Ronak Doshi
2023-04-26 16:54 ` [PATCH next 0/7] vmxnet3: upgrade " Ferruh Yigit
2023-04-26 18:15 ` Ferruh Yigit
2023-04-26 18:33 ` Ronak Doshi
2023-04-27 9:15 ` Ferruh Yigit
2023-04-28 7:05 ` Ronak Doshi
2023-05-03 10:05 ` 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=b4b8c6cd-1586-d64c-6ed4-e22fba4dc616@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).