From: mitali <mitaliyada@cse.iitb.ac.in>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: Priyanka <ppnaik@cse.iitb.ac.in>,
"users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] seg fault in InterVM communication using virtio
Date: Wed, 1 Mar 2017 19:20:37 +0530 [thread overview]
Message-ID: <63560385-2261-7213-9e7c-6acef4d290c7@cse.iitb.ac.in> (raw)
In-Reply-To: <20170223062714.GX18844@yliu-dev.sh.intel.com>
Hi,
We have some doubt regarding virtio front end. As we are running dpdk
application inside VM with virtio setup, do we need to use virtio
specific functions like virtio_recv_pkts() and virtio_xmit_pkts() to
receive and transmit packets, functions for port initialization like
virtio_dev_queue_setup()? If yes, we are unable to find any application
which uses these functions. Can you provide us some pointers on examples
which uses these functions.
Thanks,
Mitali
On Thursday 23 February 2017 11:57 AM, Yuanhan Liu wrote:
> On Wed, Feb 22, 2017 at 02:25:29PM +0530, mitali wrote:
>> Hi Yuanhan,
>>
>> We are using virt-manager to start the VMs. We are attaching the image which
>> shows the vNIC setup for the VMs.
>>
>> We have written our own dpdk application to send and receive UDP packets. The
>> command we are using is
>>
>> ./build/app/dpdkapi -c 1 -- -p 1 where dpdkapi is our application.
>>
>> Inside the application we are sending and receiving packets from vNIC using
>> rte_eth_tx_burst() and rte_eth_rx_burst().
>>
>> At the sender side after 127 packets the application stops and we observe a seg
>> fault in dmesg. Using the print statements we observed that it faults in
>> rte_eth_tx_burst(). All the 127 were received at the receiving VM.
> Would you recompile dpdk with debug info enaled, which could be done by:
>
> make ... EXTRA_CFLAGS='-g3 -O0'
>
> And run it with gdb then dump the call stack?
>
> --yliu
next prev parent reply other threads:[~2017-03-01 13:52 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
2017-02-22 8:55 ` mitali
2017-02-23 6:27 ` Yuanhan Liu
2017-03-01 13:50 ` mitali [this message]
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=63560385-2261-7213-9e7c-6acef4d290c7@cse.iitb.ac.in \
--to=mitaliyada@cse.iitb.ac.in \
--cc=dev@dpdk.org \
--cc=ppnaik@cse.iitb.ac.in \
--cc=users@dpdk.org \
--cc=yuanhan.liu@linux.intel.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).