From: "Pierre Pfister (ppfister)" <ppfister@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Enable virtio VIRTIO_RING_F_INDIRECT_DESC feature ?
Date: Fri, 2 Sep 2016 13:41:57 +0000 [thread overview]
Message-ID: <ED8610E7-EC05-4E88-9209-19F9EC438ED5@cisco.com> (raw)
Hello all,
I think http://dpdk.org/dev/patchwork/patch/5389/ disabled support of indirect buffers by accident.
Am I missing something ? Is there a reason why this was disabled ?
I tested it today and it seems to work fine.
If you have no objection, could we re-enable it ?
It is a very useful feature as it enables using more descriptors than limited by the queue size.
Thanks,
- Pierre
next reply other threads:[~2016-09-02 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 13:41 Pierre Pfister (ppfister) [this message]
2016-09-02 13:45 ` Maxime Coquelin
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=ED8610E7-EC05-4E88-9209-19F9EC438ED5@cisco.com \
--to=ppfister@cisco.com \
--cc=dev@dpdk.org \
/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).