From: Stephen Hemminger <stephen@networkplumber.org>
To: "Tim Deng" <dpdkdev@126.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Is vhost vring_avail size tunable?
Date: Tue, 9 Jun 2015 17:49:06 -0700 [thread overview]
Message-ID: <20150609174906.075e76c8@urahara> (raw)
In-Reply-To: <cb61a61.2dc8.14dcd0a7582.Coremail.dpdkdev@126.com>
On Sun, 7 Jun 2015 16:02:04 +0800 (CST)
"Tim Deng" <dpdkdev@126.com> wrote:
>
> Hi,
>
> Under heavy work load, I found there were some packet lost caused by
> "Failed to get enough desc from vring...", is there any way to get the
> vring size larger?
>
> Thanks,
> Tim
One thing that could help the DPDK virtio driver would be to support
INDIRECT descriptors. By using that, it is possible to get 256 packets
into the 256 slots in QEMU. Currently half the slots are taken by
headers.
The implementation of vhost driver likewise needs to get support
for INDIRECT descriptors and some other features in order to use slots
more efficiently.
prev parent reply other threads:[~2015-06-10 0:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 8:02 Tim Deng
2015-06-08 1:56 ` Ouyang, Changchun
2015-06-08 11:49 ` Tim Deng
2015-06-10 0:49 ` 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=20150609174906.075e76c8@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=dpdkdev@126.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).