DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ronak Doshi <doshir@vmware.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
	Jochen Behrens <jbehrens@vmware.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [PATCH next 4/7] vmxnet3: add command to set ring buffer sizes
Date: Thu, 27 Apr 2023 15:59:42 +0000	[thread overview]
Message-ID: <2CE327F8-55F5-4891-90A6-E19B70C4D642@vmware.com> (raw)
In-Reply-To: <8b65612c-e9db-95b1-4eb0-27f25383ad3a@amd.com>


> On 4/27/23, 1:51 AM, "Ferruh Yigit" <ferruh.yigit@amd.com <mailto:ferruh.yigit@amd.com>> wrote:
>
> README doesn't say much.
>
> The usage is not standard, and intention is not clear.
> Can you please dig this issue more to learn the the intention, may be we
> can find a better way or get rid of them completely?

Sure, I can take this up, but it will be better if that is investigated and done as a separate patch
as lot of definitions include those header files. The intention of this patch series is completely different,
and I don't want to break or delay this patch series. Is that OK?


Thanks, 
Ronak






  reply	other threads:[~2023-04-28  7:26 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
2023-04-26 17:27     ` Ronak Doshi
2023-04-27  8:50       ` Ferruh Yigit
2023-04-27 15:59         ` Ronak Doshi [this message]
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=2CE327F8-55F5-4891-90A6-E19B70C4D642@vmware.com \
    --to=doshir@vmware.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=jbehrens@vmware.com \
    --cc=john.mcnamara@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).