DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Singh, Aman Deep" <aman.deep.singh@intel.com>
To: Jie Wang <jie1x.wang@intel.com>, <dev@dpdk.org>
Cc: <stevex.yang@intel.com>, <qi.z.zhang@intel.com>,
	<qiming.yang@intel.com>,  <yuying.zhang@intel.com>,
	<stable@dpdk.org>
Subject: Re: [PATCH] app/testpmd: fix testpmd receive jumbo frame packets
Date: Thu, 27 Oct 2022 21:07:57 +0530	[thread overview]
Message-ID: <7642a965-4e9b-d302-7bf8-c333f3afb661@intel.com> (raw)
In-Reply-To: <20221025020510.117132-1-jie1x.wang@intel.com>

Hi Jie,

Thanks for the patch.


On 10/25/2022 7:35 AM, Jie Wang wrote:
> For NIC I40E_10G-10G_BASE_T_X722, when testpmd is configured with
> link speed, it cannot receive jumbo frame packets.

Why only the jumbo frame are effected and not other pkts.

>
> Because it has changed the link status of the ports if it was
> configured with link speed.

If we configure to same link speed, will it still have issue ?

>
> When exiting testpmd that it automatically stops packet forwarding
> and stops all the ports. But it doesn't update the link status of the
> ports. If stop the ports first that it will update the link status.
>
> This patch fix the error that testpmd will update the link status of
> the ports when it exits.
>
> Fixes: d3a274ce9dee ("app/testpmd: handle SIGINT and SIGTERM")
> Fixes: 284c908cc588 ("app/testpmd: request device removal interrupt")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jie Wang <jie1x.wang@intel.com>
> ---
>   app/test-pmd/testpmd.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c
> index 97adafacd0..c348a3f328 100644
> --- a/app/test-pmd/testpmd.c
> +++ b/app/test-pmd/testpmd.c
> @@ -3548,7 +3548,7 @@ pmd_test_exit(void)
>   	}
>   #endif
>   	if (ports != NULL) {
> -		no_link_check = 1;
> +		no_link_check = 0;
>   		RTE_ETH_FOREACH_DEV(pt_id) {
>   			printf("\nStopping port %d...\n", pt_id);
>   			fflush(stdout);
> @@ -3675,7 +3675,7 @@ rmv_port_callback(void *arg)
>   		need_to_start = 1;
>   		stop_packet_forwarding();
>   	}
> -	no_link_check = 1;
> +	no_link_check = 0;

Well, here we are undoing a previous change done for 284c908cc588
Won't that issue come back.

>   	stop_port(port_id);
>   	no_link_check = org_no_link_check;
>   


  reply	other threads:[~2022-10-27 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25  2:05 Jie Wang
2022-10-27 15:37 ` Singh, Aman Deep [this message]
2022-10-28  2:30   ` Wang, Jie1X

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=7642a965-4e9b-d302-7bf8-c333f3afb661@intel.com \
    --to=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=jie1x.wang@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=stable@dpdk.org \
    --cc=stevex.yang@intel.com \
    --cc=yuying.zhang@intel.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).