DPDK patches and discussions
 help / color / mirror / Atom feed
From: Linhaifeng <haifeng.lin@huawei.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "lixiao \(H\)" <lixiao91@huawei.com>,
	"Guofeng \(E\)" <wind.guo@huawei.com>
Subject: [dpdk-dev] Is VFIO driver's performance better than IGB_UIO?
Date: Fri, 8 Aug 2014 07:41:28 +0000	[thread overview]
Message-ID: <4099DE2E54AFAD489356C6C9161D533363BB3709@szxema505-mbx.china.huawei.com> (raw)

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.

Is something wrong with my test? My test is as follow:

1.       bind two 82599 ether to VFIO  ./tools/dpdk_nic_bind.py -b vfio-pci 03:00.0 03:00.1

2.       run the l2fwd to watch the stats info.

3.       Bind the 82599 ehter to IGB_UIO  ./tools/dpdk_nic_bind.py -b igb_uio 03:00.0 03:00.1

4.       run the l2fwd to watch the stats info.




The result of test is :（Mpps）
VFIO-64-PHY-PHY

IGBUIO-64-PHY-PHY

VFIO-512-PHY-PHY

IGBUIO-512-PHY-PHY

2.6235456

2.3467793

1.9432854

1.9432753

2.5724822

2.5405128

1.9432777

1.9432832

2.2418318

2.5154781

1.9395376

1.9432291

2.470847

2.551112

1.9432767

1.9432756

2.5092176

2.4965851

1.9432705

1.9432733

2.51572

2.4703292

1.9432637

1.9432669

2.6293656

2.472452

1.9432719

1.943283

2.480364

2.6295004

1.9432775

1.943286

2.4242182

2.613162

1.943268

1.9432663



I have two questions:

1.       If the result is wrong how can I test the VFIO and IGB_UIO

2.       If the result is normal why use VFIO?




             reply	other threads:[~2014-08-08  7:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  7:41 Linhaifeng [this message]
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

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=4099DE2E54AFAD489356C6C9161D533363BB3709@szxema505-mbx.china.huawei.com \
    --to=haifeng.lin@huawei.com \
    --cc=dev@dpdk.org \
    --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).