From: Vincent JARDIN <vincent.jardin@6wind.com>
To: Linhaifeng <haifeng.lin@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Guofeng \(E\)" <wind.guo@huawei.com>,
"lixiao \(H\)" <lixiao91@huawei.com>
Subject: Re: [dpdk-dev] Is VFIO driver's performance better than IGB_UIO?
Date: Fri, 08 Aug 2014 09:45:51 +0200 [thread overview]
Message-ID: <53E4802F.70904@6wind.com> (raw)
In-Reply-To: <4099DE2E54AFAD489356C6C9161D533363BB3709@szxema505-mbx.china.huawei.com>
On 08/08/2014 09:41, Linhaifeng wrote:
> I have test the VFIO driver and IGB_UIO driver by l2fwd for many times. I find that the VFIO driver’s performance is not better than the IGB_UIO.
You are right, under some conditions UIO is faster, VFIO provides
safety. The best solution is a PMD without UIO, neither VFIO.
which CPU are you using?
Best regards,
Vincent
next prev parent reply other threads:[~2014-08-08 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 7:41 Linhaifeng
2014-08-08 7:45 ` Vincent JARDIN [this message]
2014-08-08 7:54 ` [dpdk-dev] 答复: " Linhaifeng
2014-08-08 9:23 ` [dpdk-dev] " Vincent JARDIN
2014-08-08 18:19 ` Chris Wright
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=53E4802F.70904@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=dev@dpdk.org \
--cc=haifeng.lin@huawei.com \
--cc=lixiao91@huawei.com \
--cc=wind.guo@huawei.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).