From: Chris Wright <chrisw@redhat.com>
To: Vincent JARDIN <vincent.jardin@6wind.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, 8 Aug 2014 11:19:31 -0700 [thread overview]
Message-ID: <20140808181931.GK26743@x220.localdomain> (raw)
In-Reply-To: <53E49715.3020504@6wind.com>
* Vincent JARDIN (vincent.jardin@6wind.com) wrote:
> > My cpu is "Intel(R) Xeon(R) CPU E5620 @ 2.40GHz"
>
> It is a Westmere if I am correct. So,use UIO.
My experience is that the CPU isn't as an important part of the platform
as the chipset. IOW, VFIO requires full IOMMU isolation, and the IOMMU
cost depends on the chipset.
Vincent, is that what you were implying by cpu, or do you see something
else?
thanks,
-chris
prev parent reply other threads:[~2014-08-08 18:16 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
2014-08-08 7:54 ` [dpdk-dev] 答复: " Linhaifeng
2014-08-08 9:23 ` [dpdk-dev] " Vincent JARDIN
2014-08-08 18:19 ` Chris Wright [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=20140808181931.GK26743@x220.localdomain \
--to=chrisw@redhat.com \
--cc=dev@dpdk.org \
--cc=lixiao91@huawei.com \
--cc=vincent.jardin@6wind.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).