DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Choi, Sy Jong" <sy.jong.choi@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] vhost-switch TX corrupted packet with Fedora 21 VM
Date: Thu, 16 Apr 2015 02:55:48 +0000	[thread overview]
Message-ID: <697F8B1B48670548A5BAB03E8283550F353F35D6@PGSMSX108.gar.corp.intel.com> (raw)

Hi

Sending packets out from virtio to dpdk vhost to phy will cause packets corruption
I have tested this using 
 - DPDK 2.0.0 using vhost-cuse, 
 - qemu 1.6.1. 
 - DPDK vhost-switch sample app.

Fedara 21 (kernel 3.19), packets corrupted.
Debian Wheezy (kernel 3.2), packets are ok.

Sometime the packets was not even sent out, and I keep getting this message. 
VHOST_DATA: (0) WARNING: This device is using an existing MAC address and has not been registered
VHOST_DATA: (0) WARNING: This device is using an existing MAC address and has not been registered

I think DPDK vhost-switch filter non register MAC address.
Occasionally, packets were being forwarded by vhost-switch.

Setup is very simple, just configure IP address (1.1.1.1/24) on the VM eth0, and ping an IP address (1.1.1.2) on the same subnet with Arp table entry added.									__
    +---------------------------------------------------+   |
    |   guest                                           |   |
    |   +-------------------------------------------+   |   |
    |   |               Ping  ICMP                  |   |   |
    |   +-------------------------------------------+   |   |
    |       :                                           |   |
    |       |                                           |   |  guest
    |       v                                           |   |
    |   +-------------------------------------------+   |   |
    |   |               Kernel Virtio               |   |   |
    +---+---------------+-----------+---------------+---+ __|
            :                                   
            |                                   
            v                                            __
    +---+---------------+----------+--------------=+---+   |
    |   | vhost net0    |                              |   |
    |   +---------------+                              |   |
    |       :                                          |   |
    |       |                                          |   |  host
    |       V                                          |   |
    |   +--------------+                               |   |
    |   |   phy port   |  vhost-switch                 |   |
    +---+--------------+-------------------------------+ __|
               :                           
               |                           
               V                           
    +--------------------------------------------------+
    |                                                  |
    |                traffic generator                 |
    |                                                  |
    +--------------------------------------------------+

ICMP packet has become:-
0010: 00000000100000001050b95a81000000 0088ffff1050b95a0088ffff2050b95a
0020: 0088ffff2050b95a0088ffff3050b95a 0088ffff3050b95a0088ffff4050b95a
0030: 0088ffff4050b95a0088ffff5050b95a 0088ffff5050b95a0088ffff6050b95a
0040: 0088ffff6050b95a

Regards,
Choi, Sy Jong
Platform Application Engineer

                 reply	other threads:[~2015-04-16  2:55 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=697F8B1B48670548A5BAB03E8283550F353F35D6@PGSMSX108.gar.corp.intel.com \
    --to=sy.jong.choi@intel.com \
    --cc=dev@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).