From: Eric Kinzie <ehkinzie@gmail.com>
To: Ilya Maximets <i.maximets@samsung.com>
Cc: dev@dpdk.org, Declan Doherty <declan.doherty@intel.com>,
Heetae Ahn <heetae82.ahn@samsung.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/bonding: allow configuring jumbo frames without slaves
Date: Sun, 9 Apr 2017 22:22:26 -0400 [thread overview]
Message-ID: <20170410022225.GA5162@roosta> (raw)
In-Reply-To: <1491577632-31289-1-git-send-email-i.maximets@samsung.com>
On Fri Apr 07 18:07:12 +0300 2017, Ilya Maximets wrote:
> Currently, 'rte_eth_dev_configure' fails on attempt to setup
> max_rx_pkt_len > 2048 if no slaves was added to bonded device.
>
> For example:
>
> rte_eth_dev_attach("eth_bond0,slave=05:00.0,mode=l34", &id)
> conf.rxmode.jumbo_frame = 1;
> conf.rxmode.max_rx_pkt_len = 9000;
> rte_eth_dev_configure(id, 1, 1, &conf)
>
> Result:
> EAL: Initializing pmd_bond for eth_bond0
> EAL: Create bonded device eth_bond0 on port 4 in mode 2 on socket 0.
> rte_eth_dev_configure: ethdev port_id=4 \
> max_rx_pkt_len 9018 > max valid value 2048
>
> It's expected that slaves will be added to bonded device inside
> 'rte_eth_dev_configure' and proper 'max_rx_pktlen' configured
> for all of them.
>
> Failure happens because of hardcoded low value of 'max_rx_pktlen'.
> Increasing of this value to ETHER_MAX_JUMBO_FRAME_LEN will allow
> above scenario (attach + configure).
>
> It is important because it is the way OVS wants to work with
> all DPDK devices (including virtual).
> Changing the default hardcoded value makes no harm because
> all the slaves' related code uses only 'candidate_max_rx_pktlen'
> variable.
>
> CC: stable@dpdk.org
> Fixes: 6cfc6a4f0d61 ("net/bonding: inherit maximum Rx packet length")
> Signed-off-by: Ilya Maximets <i.maximets@samsung.com>
> ---
> drivers/net/bonding/rte_eth_bond_pmd.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/bonding/rte_eth_bond_pmd.c b/drivers/net/bonding/rte_eth_bond_pmd.c
> index c398fdb..0c8cc40 100644
> --- a/drivers/net/bonding/rte_eth_bond_pmd.c
> +++ b/drivers/net/bonding/rte_eth_bond_pmd.c
> @@ -1689,8 +1689,9 @@ bond_ethdev_info(struct rte_eth_dev *dev, struct rte_eth_dev_info *dev_info)
>
> dev_info->max_mac_addrs = 1;
>
> - dev_info->max_rx_pktlen = internals->candidate_max_rx_pktlen ?
> - internals->candidate_max_rx_pktlen : 2048;
> + dev_info->max_rx_pktlen = internals->candidate_max_rx_pktlen
> + ? internals->candidate_max_rx_pktlen
> + : ETHER_MAX_JUMBO_FRAME_LEN;
>
> dev_info->max_rx_queues = (uint16_t)128;
> dev_info->max_tx_queues = (uint16_t)512;
> --
> 2.7.4
>
Reviewed-by: Eric Kinzie <ehkinzie@gmail.com>
next prev parent reply other threads:[~2017-04-10 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170407150720eucas1p2ea1d3b1c4f1e4dd394f98ff4d8573c32@eucas1p2.samsung.com>
2017-04-07 15:07 ` Ilya Maximets
2017-04-10 2:22 ` Eric Kinzie [this message]
2017-04-14 8:31 ` Declan Doherty
2017-04-14 9:40 ` Ferruh Yigit
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=20170410022225.GA5162@roosta \
--to=ehkinzie@gmail.com \
--cc=bernard.iremonger@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=heetae82.ahn@samsung.com \
--cc=i.maximets@samsung.com \
--cc=stable@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).