From: Alex Kiselev <kiselev99@gmail.com>
To: Kyle Larose <klarose@sandvine.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] xl710 NIC doesn't receive 1518 bytes packets
Date: Fri, 26 Jan 2018 16:44:15 +0300 [thread overview]
Message-ID: <CAMKNYbzxg_eEY9X-wBdFSS2uVx84_X4++NbHZxwTSyUePb2v4g@mail.gmail.com> (raw)
In-Reply-To: <CAMKNYby5zuYxe=mmS+7d8X02ZpFzRxX5AhySbonXt1+Zw8Wmgw@mail.gmail.com>
2018-01-24 17:14 GMT+03:00 Alex Kiselev <kiselev99@gmail.com>:
> Hi Kyle.
>
> 2018-01-24 17:01 GMT+03:00 Kyle Larose <klarose@sandvine.com>:
>> Did you set the MTU on the bond port? It has separate configuration IIRC.
I don't see any special API functions for setting MTU of a bonding
port neither in 17.08.1
that I am currently using nor in the latest DPDK branch.
So, I use regular MTU setting function rte_eth_dev_set_mtu() for my
bond port created via command line arguments.
And It doesn't work. 1518 bytes packets are being filtered.
I tried to hardcode setting MTU for each slave port and it solved the
problem. So, it looks like
the problem is the rte_eth_dev_set_mtu() call that doesn't change MTU
of slave ports when it is called
for a bonding port.
The described problem exists at least with i40e driver and doesn't
show up when I use x520 NICS.
--
Alex Kiselev
next prev parent reply other threads:[~2018-01-26 13:44 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
2018-01-24 14:01 ` Kyle Larose
2018-01-24 14:14 ` Alex Kiselev
2018-01-26 13:44 ` Alex Kiselev [this message]
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=CAMKNYbzxg_eEY9X-wBdFSS2uVx84_X4++NbHZxwTSyUePb2v4g@mail.gmail.com \
--to=kiselev99@gmail.com \
--cc=klarose@sandvine.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).