All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent JARDIN <vincent.jardin-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Linhaifeng <haifeng.lin-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org"
	<dev-VfR2kkLFssw@public.gmane.org>,
	"Guofeng \(E\)"
	<wind.guo-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	"lixiao \(H\)" <lixiao91-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: Re: 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-mfeVThRg90OEZbDCDsDlKQK1hpo4iccwjNknBlVQO8k@public.gmane.org>

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

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  7:41 Is VFIO driver's performance better than IGB_UIO? Linhaifeng
     [not found] ` <4099DE2E54AFAD489356C6C9161D533363BB3709-mfeVThRg90OEZbDCDsDlKQK1hpo4iccwjNknBlVQO8k@public.gmane.org>
2014-08-08  7:45   ` Vincent JARDIN [this message]
     [not found]     ` <53E4802F.70904-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-08-08  7:54       ` 答复: " Linhaifeng
     [not found]         ` <4099DE2E54AFAD489356C6C9161D533363BB4727-mfeVThRg90OEZbDCDsDlKQK1hpo4iccwjNknBlVQO8k@public.gmane.org>
2014-08-08  9:23           ` Vincent JARDIN
     [not found]             ` <53E49715.3020504-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
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-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=haifeng.lin-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=lixiao91-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=wind.guo-hv44wF8Li93QT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.