All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prakash B <bjsprakash.linux@gmail.com>
To: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
	Peter Maydell <peter.maydell@linaro.org>,
	Eric Auger <eric.auger@redhat.com>,
	Sunil Goutham <sgoutham@cavium.com>,
	bprakash@caviumnetworks.com, berrange@redhat.com
Subject: [Qemu-devel] Virito devices bridge vs Macvtap performance
Date: Thu, 5 Apr 2018 11:39:41 +0530	[thread overview]
Message-ID: <CACJhumcLYPhMkO5idkL0eW6nsdbwhFv3KMWi9c5Q5bPv_2Rq6g@mail.gmail.com> (raw)

Hi,

I am doing kvm guest network performance analysis to compare relevant
alternatives for  virtio devices on Arrach64.

I have generated bridge tap and macvtap performance numbers  on guest
10G interface
connected back to  another 10G on other host.

The results for guest with  "macvtap" vs  "bridge" are  marginally
differed and the difference is +/- 3%. As per my understanding on
macvtap, expected better performance values with macvtap.


--------------------<Begin of commands > --------------------
for  macvtap device:-
-netdev tap,vhost=on,vhostforce=on,id=macvtap_netdev,fd=3
3<>/dev/tap$(cat /sys/class/net/macvtap1/ifindex)  \
 -device virtionet-pci,netdev=macvtap_netdev,id=net0,mac=$(cat
/sys/class/net/macvtap1/address)

for Bridge tap device:-
-netdev type=tap,vhost=on,vhostforce=on,id=tap0,ifname=tap0,script=no,downscript=no
-device virtio-net-pci,netdev=tap0,mac=12:03:04:05:06:07

-----------------------< End of commands> ------------------------

Anyone please tell me if I missed anything.

Other information.
-------------------------
Kernel sources :  4.14.28
qemu-aarch64 :  2.11.91

Did the same  experiments with ThunderX vnic and Intel 10G nic and
results are as mentioned above.
Tried macvtap in bridge and passthru modes.


Tell me if  you  need further investigations or more data .

thanks,
Prakash B

                 reply	other threads:[~2018-04-05  6:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CACJhumcLYPhMkO5idkL0eW6nsdbwhFv3KMWi9c5Q5bPv_2Rq6g@mail.gmail.com \
    --to=bjsprakash.linux@gmail.com \
    --cc=berrange@redhat.com \
    --cc=bprakash@caviumnetworks.com \
    --cc=eric.auger@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sgoutham@cavium.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 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.