DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Priyanka <ppnaik@cse.iitb.ac.in>
Cc: "users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>,
	"mitaliyada@cse.iitb.ac.in" <mitaliyada@cse.iitb.ac.in>
Subject: Re: [dpdk-dev] seg fault in InterVM communication using virtio
Date: Wed, 22 Feb 2017 16:43:23 +0800	[thread overview]
Message-ID: <20170222084323.GP18844@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <58AAC534.7000004@cse.iitb.ac.in>

On Mon, Feb 20, 2017 at 04:00:12PM +0530, Priyanka wrote:
> Hi All,
> 
> We have 2 VM running on qemu-kvm hypervisor. We have provided vNIC to the
> VMs using macvtap device and virtio as the device model in bridge mode. We
> are running DPDK applications (udp client and server) on the VMs. We observe
> that the inter-VM communication is not happening using drivers i.e igb_uio
> and uio_pci_generic. We were able to communicate between the VMs properly
> using SRIOV. But we were not getting performance as expected so we switched
> to virtio. But using virtio the DPDK communication hangs after sending 128
> packets. We also observe a seg fault in the dmesg of the VM.
> 
> Please provide us some guideline to do the inter-VM communication using
> virtio. Are we correct if we are using rte_eth_tx/rx_burst to send and
> receive packets from the vNIC.

Would you provide more info, say how do you start the vm, and how do you
run the dpdk apps? Providing all the commands that could reproduce your
issue will be better.

	--yliu

  reply	other threads:[~2017-02-22  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 10:30 Priyanka
2017-02-22  8:43 ` Yuanhan Liu [this message]
2017-02-22  8:55   ` mitali
2017-02-23  6:27     ` Yuanhan Liu
2017-03-01 13:50       ` mitali
2017-03-02 12:23         ` Yuanhan Liu
2017-03-02 12:32           ` mitali
2017-03-02 12:59             ` Yuanhan Liu
2017-03-02 14:00               ` mitali
2017-03-02 11:13       ` ppnaik

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=20170222084323.GP18844@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=dev@dpdk.org \
    --cc=mitaliyada@cse.iitb.ac.in \
    --cc=ppnaik@cse.iitb.ac.in \
    --cc=users@dpdk.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).