From: Shirley Avishour <shirley@imvisiontech.com>
To: dev@dpdk.org
Subject: [dpdk-dev] using virtio driver in dpdk release 2.0
Date: Tue, 19 Jul 2016 18:00:27 +0300 [thread overview]
Message-ID: <CACn717h9vQzuGDhvRm=QZ5bOMUkStAzRkPXwGMVRU+EkK2CSFA@mail.gmail.com> (raw)
Hi,
We are using KVM for loading our VM using e1000 driver for the VM interface.
we noticed that the maximum rate (rx/tx) I get is 10Mbps.
I am currently attempting to move to virtio driver using dpdk release 2.0.
>From the documentation it seems that I have to load my dpdk application
with librte_pmd_virtio.so.
1) The Makefile under lib/librte_pmd_virtio creates a static library. do I
have to write another Makefile for shared object?
2) there is a known bug regarding application taking control of the kernel
managed virtio device, and it seems that there is a patch for this bug only
for release 16.04 - is that correct? is there a patch for release 2.0 as
well?
http://dpdk.org/dev/patchwork/patch/12462/
3) I tried to run my application with the librte_pmd_virtio.so which I
compiled but the application fails to load the interfaces. is it a known
issue in release 2.0?
thanks.
reply other threads:[~2016-07-19 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CACn717h9vQzuGDhvRm=QZ5bOMUkStAzRkPXwGMVRU+EkK2CSFA@mail.gmail.com' \
--to=shirley@imvisiontech.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).