From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v3] netvsc: resize event buffer as needed
Date: Thu, 23 Aug 2018 16:59:43 +0100 [thread overview]
Message-ID: <ce7bbd5d-8e13-4940-61b7-59f89a1b5fb8@intel.com> (raw)
In-Reply-To: <20180814164525.10703-1-stephen@networkplumber.org>
On 8/14/2018 5:45 PM, Stephen Hemminger wrote:
> The event buffer was changed to be a fixed size value,
> had a couple of issues. The big one is that rte_free was still
> being called for a pointer that was not setup with rte_malloc().
>
> The event buffer was also too small to handle heavy receive
> traffic; and running the event buffer out would crash
> the application.
>
> Fix by going back to a dynamically resized event buffer.
> And grow it by 25% to avoid lots of realloc's.
>
> Fixes: 530af95a7849 ("bus/vmbus: avoid signalling host on read")
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
Cc: stable@dpdk.org
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-08-23 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 16:45 Stephen Hemminger
2018-08-23 15:59 ` 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=ce7bbd5d-8e13-4940-61b7-59f89a1b5fb8@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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).