qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Mihai Donțu" <mihai.dontu@gmail.com>
To: "Maurício Almeida" <malmeida@inf.ufsm.br>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Doubts about Kvm architecture
Date: Wed, 31 May 2017 20:48:55 +0300	[thread overview]
Message-ID: <1496252935.14809.59.camel@gmail.com> (raw)
In-Reply-To: <CAEB0U7On7OPAytSMjx94pfMKswuEzrty87Asz_9TYV_wrc4p4w@mail.gmail.com>

On Wed, 2017-05-31 at 14:09 -0300, Maurício Almeida wrote:
> My name is Maurício, we are making a study about Kvm Paravirtualized
> and Full virtualized at our University, we are from University Federal
> of Santa Maria.
> Can you give us some papers about how the Kvm or Qemu executes the I/O
> Network with one emulated Device?
> 
> We executed some tests using Virtio Driver and e1000 emulated driver,
> the network output of Virtio is normal and use four of the four
> Machine Cpu's, but the output of e1000 Emulated driver was too low
> about Virtio and It onlyused one of the four machine cpu's during the
> network test execution.
> The Traffic of Virtio was 956 MB/s while e1000 Emulated Driver was 192
> MB/s, both using Packet size of 1518 Bytes.
> 
> Why when it used e1000 Emulated Driver the traffic was to low and use
> only one Cpu all the time?
> Do Qemu or Kvm Guest need some specific configuration to use all CPU's?
> 
> Do you have any paper where we can find in details if Qemu is limited
> to use one CPU when use Network Emulated Driver?

A cursory look over the qemu e1000 driver would suggest that it does
not support multithreading. virtio largely bypasses the qemu hw
machinery.

-- 
Mihai Donțu

       reply	other threads:[~2017-05-31 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEB0U7On7OPAytSMjx94pfMKswuEzrty87Asz_9TYV_wrc4p4w@mail.gmail.com>
2017-05-31 17:48 ` Mihai Donțu [this message]
2017-05-31 16:56 [Qemu-devel] Doubts about Kvm architecture Maurício Almeida
2017-05-31 21:44 ` Eric Blake

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=1496252935.14809.59.camel@gmail.com \
    --to=mihai.dontu@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=malmeida@inf.ufsm.br \
    --cc=qemu-devel@nongnu.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).