From: gowrishankar <gowrishankar.m@linux.vnet.ibm.com>
To: "Du, Fan" <fan.du@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"dev@openvswitch.org" <dev@openvswitch.org>
Subject: Re: [dpdk-dev] [ovs-dev] dpdkvhostuser fail to alloc memory when receive packet from other host
Date: Wed, 17 Jun 2015 17:24:10 +0530 [thread overview]
Message-ID: <55815FE2.9060301@linux.vnet.ibm.com> (raw)
In-Reply-To: <5A90DA2E42F8AE43BC4A093BF0678848E6C4D8@SHSMSX104.ccr.corp.intel.com>
On Wednesday 17 June 2015 03:19 PM, Du, Fan wrote:
> Hi,
>
> I'm playing dpdkvhostuser ports with latest DPDK and ovs master tree with iperf benchmarking.
> When kvm guest1(backed up dpdkvhostuser port)siting on HOST1 is receiving packets from either other physical HOST2,
> or similar kvm guest2 with dpdkvhostuser port siting on HOST2. The connectivity will break, iperf show no bandwidth and stall finally.
In my setup where kvm guest1 receives packets from phy host through ovs
switch (vhost-user),
I do not find this problem. I am on top of below commit fyi.
commit 7d1ced01772de541d6692c7d5604210e274bcd37 (ovs)
Btw, I checked tx case for guest as well. qemu I am using is of version
2.3.0. Is your qemu of version above 2.2
if allotting more than 1GB guest memory.
Could you also share hugepages params passed to kernel.
Regards,
Gowri Shankar
>
> Other test scenario like, two kvm guest sitting on one host, or a single kvm guest send packets to a physical host works like a charm.
>
> Swiitch debug option on, dpdk lib spit as below:
> VHOST_CONFIG: read message VHOST_USER_SET_VRING_CALL
> VHOST_CONFIG: vring call idx:0 file:62
> VHOST_CONFIG: read message VHOST_USER_SET_VRING_CALL
> VHOST_CONFIG: vring call idx:0 file:58
>
> VHOST_DATA: F0 Failed to allocate memory for mbuf. mbuf_pool:0x7fc7411ab5c0
> VHOST_DATA: F0 Failed to allocate memory for mbuf. mbuf_pool:0x7fc7411ab5c0
> VHOST_DATA: F0 Failed to allocate memory for mbuf. mbuf_pool:0x7fc7411ab5c0
> VHOST_DATA: F0 Failed to allocate memory for mbuf. mbuf_pool:0x7fc7411ab5c0
> VHOST_DATA: F0 Failed to allocate memory for mbuf. mbuf_pool:0x7fc7411ab5c0
> VHOST_DATA: F0 Failed to allocate memory for mbuf. mbuf_pool:0x7fc7411ab5c0
> VHOST_DATA: F0 Failed to allocate memory for mbuf. mbuf_pool:0x7fc7411ab5c0
> VHOST_DATA: F0 Failed to allocate memory for mbuf. mbuf_pool:0x7fc7411ab5c0
>
> After some tweaks of logging code, and looks like bad things happens within below code snippet:
> In lib/librte_vhost/vhost_rxtx.c function: rte_vhost_dequeue_burst
>
> 612 vb_offset = 0;
> 613 vb_avail = desc->len;
> 614 /* Allocate an mbuf and populate the structure. */
> 615 m = rte_pktmbuf_alloc(mbuf_pool);
> 616 if (unlikely(m == NULL)) {
> 617 RTE_LOG(ERR, VHOST_DATA,
> 618 "F0 Failed to allocate memory for mbuf. mbuf_pool:%p\n", mbuf_pool);
> 619 break;
> 620 }
> 621 seg_offset = 0;
> 622 seg_avail = m->buf_len - RTE_PKTMBUF_HEADROOM;
> 623 cpy_len = RTE_MIN(vb_avail, seg_avail);
>
>
>
> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev
next prev parent reply other threads:[~2015-06-17 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 9:49 [dpdk-dev] " Du, Fan
2015-06-17 11:54 ` gowrishankar [this message]
2015-06-18 8:47 ` [dpdk-dev] [ovs-dev] " Du, Fan
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=55815FE2.9060301@linux.vnet.ibm.com \
--to=gowrishankar.m@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
--cc=dev@openvswitch.org \
--cc=fan.du@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).