From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yong Wang <yongwang@vmware.com>, Shraddha Joshi <jshraddha@vmware.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: increase rx data ring descriptor size
Date: Thu, 19 Apr 2018 23:57:50 +0100 [thread overview]
Message-ID: <e4ac61c9-cd25-ad5a-af73-0f59d55ec777@intel.com> (raw)
In-Reply-To: <BY2PR05MB235946D7E91FA0F0845F969DAFB50@BY2PR05MB2359.namprd05.prod.outlook.com>
On 4/19/2018 10:54 PM, Yong Wang wrote:
>> -----Original Message-----
>> From: Shraddha Joshi [mailto:jshraddha@vmware.com]
>> Sent: Thursday, April 19, 2018 11:19 AM
>> To: Yong Wang <yongwang@vmware.com>
>> Cc: dev@dpdk.org; Shraddha Joshi <jshraddha@vmware.com>
>> Subject: [PATCH] net/vmxnet3: increase rx data ring descriptor size
>>
>> Vmxnet3 driver supports receive data ring viz. a set of small sized
>> buffers that are always mapped by the emulation. If a packet fits into
>> the receive data ring buffer, the emulation delivers the packet via the
>> receive data ring.
>>
>> Increasing the receive data ring descriptor size from 128 to 256
>> showed performance gains as high as 5% for packets smaller than 256.
>>
>> Signed-off-by: Shraddha Joshi <jshraddha@vmware.com>
>> Acked-by: Jin Heo <heoj@vmware.com>
>> Acked-by: Guolin Yang <gyang@vmware.com>
>> Acked-by: Boon Ang <bang@vmware.com>
>
> Acked-by: Yong Wang <yongwang@vmware.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-04-19 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 18:19 Shraddha Joshi
2018-04-19 21:54 ` Yong Wang
2018-04-19 22:57 ` Ferruh Yigit [this message]
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=e4ac61c9-cd25-ad5a-af73-0f59d55ec777@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jshraddha@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).