From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Walter Heymans <walter.heymans@corigine.com>, <dev@dpdk.org>
Cc: "Niklas Söderlund" <niklas.soderlund@corigine.com>,
"Louis Peens" <louis.peens@corigine.com>,
"Chaoyong He" <chaoyong.he@corigine.com>,
"Richard Donkin" <richard.donkin@corigine.com>
Subject: Re: [PATCH v2] net/nfp: update how MAX MTU is read
Date: Tue, 3 May 2022 20:04:48 +0100 [thread overview]
Message-ID: <ec38e46d-0e62-3423-b897-078169fb09b9@xilinx.com> (raw)
In-Reply-To: <20220420134638.24010-1-walter.heymans@corigine.com>
On 4/20/2022 2:46 PM, Walter Heymans wrote:
> The 'max_rx_pktlen' value was previously read from hardware, which was
> set by the running firmware. This caused confusion due to different
> meanings of 'MAX_MTU'. This patch updates the 'max_rx_pktlen' to the
> maximum value that the NFP NIC can support. The 'max_mtu' value that is
> read from hardware, is assigned to the 'dev_info->max_mtu' variable.
>
> If more layer 2 metadata must be used, the firmware can be updated to
> report a smaller 'max_mtu' value.
>
> The constant defined for NFP_FRAME_SIZE_MAX is derived for the maximum
> supported buffer size of 10240, minus 136 bytes that is reserved by the
> hardware and another 56 bytes reserved for expansion in firmware. This
> results in a usable maximum packet length of 10048 bytes.
>
> Signed-off-by: Walter Heymans <walter.heymans@corigine.com>
> Signed-off-by: Niklas Söderlund <niklas.soderlund@corigine.com>
> Reviewed-by: Louis Peens <louis.peens@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Richard Donkin <richard.donkin@corigine.com>
> ---
> drivers/net/nfp/nfp_common.c | 11 ++++++++++-
> drivers/net/nfp/nfp_common.h | 3 +++
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/nfp/nfp_common.c b/drivers/net/nfp/nfp_common.c
> index b26770dbfb..52fbda1a79 100644
> --- a/drivers/net/nfp/nfp_common.c
> +++ b/drivers/net/nfp/nfp_common.c
> @@ -692,7 +692,16 @@ nfp_net_infos_get(struct rte_eth_dev *dev, struct rte_eth_dev_info *dev_info)
> dev_info->max_rx_queues = (uint16_t)hw->max_rx_queues;
> dev_info->max_tx_queues = (uint16_t)hw->max_tx_queues;
> dev_info->min_rx_bufsize = RTE_ETHER_MIN_MTU;
> - dev_info->max_rx_pktlen = hw->max_mtu;
> + /*
> + * The maximum rx packet length (max_rx_pktlen) is set to the
> + * maximum supported frame size that the NFP can handle. This
> + * includes layer 2 headers, CRC and other metadata that can
> + * optionally be used.
> + * The maximum layer 3 MTU (max_mtu) is read from hardware,
> + * which was set by the firmware loaded onto the card.
> + */
> + dev_info->max_rx_pktlen = NFP_FRAME_SIZE_MAX;
> + dev_info->max_mtu = hw->max_mtu;
Hi Walter,
ethdev uses 'max_mtu' and 'max_rx_pktlen' to calculate the frame
overhead, like:
'overhead_len = max_rx_pktlen - max_mtu;'
In above change 'max_rx_pktlen' is hardcoded but 'max_mtu' is 'hw'
depended, can you confirm 'hw->max_mtu' will always have the frame
overhead as according above calculation?
> /* Next should change when PF support is implemented */
> dev_info->max_mac_addrs = 1;
>
> diff --git a/drivers/net/nfp/nfp_common.h b/drivers/net/nfp/nfp_common.h
> index 8b35fa119c..8db5ec23f8 100644
> --- a/drivers/net/nfp/nfp_common.h
> +++ b/drivers/net/nfp/nfp_common.h
> @@ -98,6 +98,9 @@ struct nfp_net_adapter;
> /* Number of supported physical ports */
> #define NFP_MAX_PHYPORTS 12
>
> +/* Maximum supported NFP frame size (MTU + layer 2 headers) */
> +#define NFP_FRAME_SIZE_MAX 10048
> +
> #include <linux/types.h>
> #include <rte_io.h>
>
next prev parent reply other threads:[~2022-05-03 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 13:46 Walter Heymans
2022-04-27 8:37 ` Niklas Söderlund
2022-04-27 9:47 ` Ferruh Yigit
2022-04-27 18:05 ` Niklas Söderlund
2022-05-03 19:04 ` Ferruh Yigit [this message]
2022-05-04 11:48 ` Walter Heymans
2022-05-10 12:51 ` 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=ec38e46d-0e62-3423-b897-078169fb09b9@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=louis.peens@corigine.com \
--cc=niklas.soderlund@corigine.com \
--cc=richard.donkin@corigine.com \
--cc=walter.heymans@corigine.com \
/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).