From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] netvsc: resize event buffer as needed
Date: Mon, 13 Aug 2018 10:22:27 -0700 [thread overview]
Message-ID: <20180813102227.09a26d5e@xeon-e3> (raw)
In-Reply-To: <20180813155108.6460-3-stephen@networkplumber.org>
On Mon, 13 Aug 2018 08:51:08 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> The event buffer was changed to be a fixed size value, but it
> is not large enough for a forwarding stress test.
>
> This version of event buffer code uses malloc/realloc to size
> the event buffer as needed. Malloc is preferred over rte_malloc
> because the event buffer does not need to be used for DMA
> and huge page is a limited resource.
>
> Fixes: 530af95a7849 ("bus/vmbus: avoid signalling host on read")
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
Self NAK. This won't work when secondary process needs the buffer.
prev parent reply other threads:[~2018-08-13 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 15:51 [dpdk-dev] [PATCH v2 0/2] netvsc: event buffer bug fixes Stephen Hemminger
2018-08-13 15:51 ` [dpdk-dev] [PATCH v2 1/2] netvsc: fix rte malloc pool corruption Stephen Hemminger
2018-08-13 15:51 ` [dpdk-dev] [PATCH v2 2/2] netvsc: resize event buffer as needed Stephen Hemminger
2018-08-13 17:22 ` Stephen Hemminger [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=20180813102227.09a26d5e@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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).