DPDK usage discussions
 help / color / mirror / Atom feed
From: "Du, Fan" <fan.du@intel.com>
To: users@dpdk.org
Cc: discuss@openvswitch.org
Subject: [dpdk-users] ARP reply packet fail to transmit on the wire on 82599ES
Date: Tue, 20 Oct 2015 14:05:42 +0800	[thread overview]
Message-ID: <5625D9B6.3010409@intel.com> (raw)

hi dpdk and ovs experts

My test bed is pretty simple, setup host1 and host2 with following topology.
I use dpdk-2.0.0 with ovs head commit.

On host1:
kvm guest1 -> dpdkvhostuser -> br-int -> vxlan port -> br-ex -> dpdk port
ifconfig br-ex 192.168.1.2/24

On host2:
kvm guest2 -> dpdkvhostuser -> br-int -> vxlan port -> br-ex -> dpdk port
ifconfig br-ex 192.168.1.4/24

All ovs bridge are on user space, both hosts are connected with DAC 
using 82599ES,
the first packet between guest1 and guest2 triggers arp resolution for 
the vxlan
outer mac address for br-ex ip address.

tcpdump on host1 br-ex with dummy device:
09:32:58.393875 ARP, Request who-has 192.168.1.4 tell 192.168.1.2, length 28

tcpdump on host2 br-ex with dummy device:
21:21:31.766201 ARP, Request who-has 192.168.1.4 tell 192.168.1.2, length 46
21:21:31.766273 ARP, Reply 192.168.1.4 is-at 90:e2:ba:64:f4:05, length 46

It's wired that host1 failed receive ARP Reply packet from host2, so 
guest1 and
guest2 cannot talk to each other. When I replace dpdk port with normal 
net device
ens803f1 using the same NIC physical port, two guests talk to each other 
well.

After some digging, the ARP reply packet did reach on ixgbe tx_pkt_burst 
function,
whether or not RTE_IXGBE_INC_VECTOR is set, ARP reply packet didn't show 
on wire.

This looks like a bug to me, or am I missing something somewhere obviously.
Any suggestions and pointers is appreciated.

             reply	other threads:[~2015-10-20  6:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  6:05 Du, Fan [this message]
2015-10-20 14:13 ` [dpdk-users] [ovs-discuss] " Chandran, Sugesh

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=5625D9B6.3010409@intel.com \
    --to=fan.du@intel.com \
    --cc=discuss@openvswitch.org \
    --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).