From: Shrikrishna Khare <skhare@shri-linux.eng.vmware.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Shrikrishna Khare <skhare@vmware.com>, <dev@dpdk.org>,
<yongwang@vmware.com>
Subject: Re: [dpdk-dev] [PATCH v2 4/7] net/vmxnet3: add receive data ring support
Date: Mon, 6 Mar 2017 14:57:03 -0800 [thread overview]
Message-ID: <alpine.DEB.2.10.1703061455300.24619@shri-linux.eng.vmware.com> (raw)
In-Reply-To: <99267906.uSrR0Gm93P@xps13>
On Mon, 6 Mar 2017, Thomas Monjalon wrote:
> 2017-03-06 09:17, Shrikrishna Khare:
> > Receive Data Ring buffer length is configurable via ethtool -G ethX rx-mini
>
> Are you configuring the ring length before unbinding from the kernel driver?
Changing rx data ring requires changing the code and recompiling.
The above ethtool -G line was from my patch that added similar feature to
Linux vmxnet3 driver. Have removed the line and reposted v3 of the patch
series.
Thanks,
Shri
next prev parent reply other threads:[~2017-03-06 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 17:17 [dpdk-dev] [PATCH v2 0/7] vmxnet3: upgrade to version 3 Shrikrishna Khare
2017-03-06 17:17 ` [dpdk-dev] [PATCH v2 1/7] net/vmxnet3: prepare for version 3 changes Shrikrishna Khare
2017-03-06 17:17 ` [dpdk-dev] [PATCH v2 2/7] net/vmxnet3: introduce generalized cmd interface Shrikrishna Khare
2017-03-06 17:17 ` [dpdk-dev] [PATCH v2 3/7] net/vmxnet3: variable length transmit data ring Shrikrishna Khare
2017-03-06 17:17 ` [dpdk-dev] [PATCH v2 4/7] net/vmxnet3: add receive data ring support Shrikrishna Khare
2017-03-06 22:24 ` Thomas Monjalon
2017-03-06 22:57 ` Shrikrishna Khare [this message]
2017-03-06 17:17 ` [dpdk-dev] [PATCH v2 5/7] net/vmxnet3: add reserved version 3 command Shrikrishna Khare
2017-03-06 17:17 ` [dpdk-dev] [PATCH v2 6/7] net/vmxnet3: add cmd to register memory region Shrikrishna Khare
2017-03-06 17:17 ` [dpdk-dev] [PATCH v2 7/7] net/vmxnet3: update to version 3 Shrikrishna Khare
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=alpine.DEB.2.10.1703061455300.24619@shri-linux.eng.vmware.com \
--to=skhare@shri-linux.eng.vmware.com \
--cc=dev@dpdk.org \
--cc=skhare@vmware.com \
--cc=thomas.monjalon@6wind.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).