DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kiran KN <kirankn@juniper.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] net/af_packet: changes to accomodate jumbo frames
Date: Wed, 6 May 2020 23:50:35 +0100	[thread overview]
Message-ID: <c408612b-a3c8-46f6-8ff2-9d875e50a697@intel.com> (raw)
In-Reply-To: <4725E5D1-40EC-4CF5-AC95-DE0DDA41C228@juniper.net>

On 4/21/2020 8:50 AM, Kiran KN wrote:
> 
> Change the maximum packet length to accommodate jumbo frames
> 
> signed-off-by: Kiran KN <kirankn@juniper.net>
> 
> ---
>  drivers/net/af_packet/rte_eth_af_packet.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/af_packet/rte_eth_af_packet.c b/drivers/net/af_packet/rte_eth_af_packet.c
> index f5806bf42..7fe3a28a7 100644
> --- a/drivers/net/af_packet/rte_eth_af_packet.c
> +++ b/drivers/net/af_packet/rte_eth_af_packet.c
> @@ -312,7 +312,7 @@ eth_dev_info(struct rte_eth_dev *dev, struct rte_eth_dev_info *dev_info)
>  
>  	dev_info->if_index = internals->if_index;
>  	dev_info->max_mac_addrs = 1;
> -	dev_info->max_rx_pktlen = (uint32_t)ETH_FRAME_LEN;
> +	dev_info->max_rx_pktlen = (uint32_t)RTE_ETHER_MAX_JUMBO_FRAME_LEN;
>  	dev_info->max_rx_queues = (uint16_t)internals->nb_queues;
>  	dev_info->max_tx_queues = (uint16_t)internals->nb_queues;
>  	dev_info->min_rx_bufsize = 0;
> 

Hi Kiran,

What is the intention of the patch, to be more accurate or to enable receiving
packets larger than 1500 bytes?

If intention is to receive large packets not sure if this change on its own
enables it,
a) PMD doesn't announce RX_OFFLOAD_JUMBO_FRAME, so 'rte_eth_dev_configure()'
can't configure the larger than 'RTE_ETHER_MAX_LEN' anyway
b) PMD '.dev_configure' dev_ops is empty, even you pass larger Rx packet length,
PMD won't configure underneath interface.
So I think the required change is more than this patch.

To get larger packets, need to call 'rte_eth_dev_set_mtu()' to set underneath
interface MTU to be able to get larger packets, which is independent from
'max_rx_pktlen'.


And for to be more accurate option, isn't the real max Rx packet size limitation
of the PMD is 'tp_frame_size'?
And from interface point of view, is the jumbo frame length really the max, can
the GRO be enabled for the interface, in that case I don't know what can be the
max Rx packet length.

      reply	other threads:[~2020-05-06 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21  7:50 Kiran KN
2020-05-06 22:50 ` Ferruh Yigit [this message]

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=c408612b-a3c8-46f6-8ff2-9d875e50a697@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=kirankn@juniper.net \
    --cc=linville@tuxdriver.com \
    --cc=thomas@monjalon.net \
    /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).