DPDK usage discussions
 help / color / mirror / Atom feed
From: Alex Kiselev <kiselev99@gmail.com>
To: users <users@dpdk.org>
Subject: Re: [dpdk-users] xl710 NIC doesn't receive 1518 bytes packets
Date: Wed, 24 Jan 2018 16:50:34 +0300	[thread overview]
Message-ID: <CAMKNYbyAJUP3oHoSXXVWgKz+dmaFnpraWxn34rpSN3Xx7rpXpw@mail.gmail.com> (raw)
In-Reply-To: <CAMKNYbzOBupbKBfNdY-UtTWRaM3oKA5cdCrGygGZtoJO6bBw0A@mail.gmail.com>

The issue with receiving 1518 byte packets is half resolved. It was an
MTU problem. I moved rte_eth_dev_set_mtu() before the
rte_dev_dev_start and it helped. Thanks to Alex _
<asb.tyum@gmail.com>.
So, 1518 packets now are successfully sent and received.

But, now I've got the same problem with the bonding driver. I created
a bond port with four i40e slave ports and place it in the LACP mode.
And the bond port doesn't receive 1518 bytes packets.

Please, help me to resolve the issue.

2018-01-24 0:44 GMT+03:00 Alex Kiselev <kiselev99@gmail.com>:
> Hi.
>
> It seems that xl710 NIC doesn't receive 1518 (maximum MTU size 1500 +
> dot1q ethernet header
> 18 bytes) bytes packets. And there is no such problem when I use x520 NIC.
>
> I am sending ipv4 ICMP ping packets and I am sure that packets go out
> from the port
> on the switch to which my application is connected. This is the
> tcpdump output from the mirror port:
>
> 00:17:52.644171 f8:32:e4:72:61:1b > 68:05:ca:30:61:80, ethertype
> 802.1Q (0x8100), length 1518: vlan 10, p 0, ethertype IPv4, (tos 0x0,
> ttl 64, id 630, offset 0, flags [DF], proto ICMP (1), length 1500)
>     1.0.0.2 > 1.0.0.1: ICMP echo request, id 5386, seq 7, length 1480
>
> And I if send 1514 bytes packets everything is also ok
>
> h7 ~ # ip netns exec bs1 ping -s 1468 1.0.0.1
> PING 1.0.0.1 (1.0.0.1) 1468(1496) bytes of data.
> 1476 bytes from 1.0.0.1: icmp_seq=1 ttl=64 time=0.935 ms
>
> tcpdump on mirror switch port for 1514 bytes (ping 1468):
>
> 00:28:15.890543 f8:32:e4:72:61:1b > 68:05:ca:30:61:80, ethertype
> 802.1Q (0x8100), length 1514: vlan 10, p 0, ethertype IPv4, (tos 0x0,
> ttl 64, id 22101, offset 0, flags [DF], proto ICMP (1), length 1496)
>     1.0.0.2 > 1.0.0.1: ICMP echo request, id 5389, seq 1, length 1476
> 00:28:15.890548 68:05:ca:30:61:80 > f8:32:e4:72:61:1b, ethertype
> 802.1Q (0x8100), length 1514: vlan 10, p 0, ethertype IPv4, (tos 0x0,
> ttl 64, id 22101, offset 0, flags [DF], proto ICMP (1), length 1496)
>     1.0.0.1 > 1.0.0.2: ICMP echo reply, id 5389, seq 1, length 1476
>
> I’ve tried to use rte_eth_dev_set_mtu() with different parameters
> but nothing has changed.
>
> Have I missed something to configure?
>
> Thanks.
>
> --
> Alex Kiselev



-- 
--
Kiselev Alexander

  reply	other threads:[~2018-01-24 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 21:44 Alex Kiselev
2018-01-24 13:50 ` Alex Kiselev [this message]
2018-01-24 14:01   ` Kyle Larose
2018-01-24 14:14     ` Alex Kiselev
2018-01-26 13:44       ` Alex Kiselev
2018-01-26 13:47         ` Kyle Larose
2018-01-26 13:52           ` Alex Kiselev
2018-02-06 12:56             ` Don maillist

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=CAMKNYbyAJUP3oHoSXXVWgKz+dmaFnpraWxn34rpSN3Xx7rpXpw@mail.gmail.com \
    --to=kiselev99@gmail.com \
    --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).