DPDK patches and discussions
 help / color / mirror / Atom feed
From: Balbeer Tiwari <Balbeer.Tiwari@radisys.com>
To: Asaf Penso <asafp@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Packet drop/Out of sequence issue with Jumbo frames on MLX ConnectX-4 Lx NIC
Date: Tue, 20 Jul 2021 15:17:50 +0000	[thread overview]
Message-ID: <MWHPR08MB28783212FB478930E8E60E0293E29@MWHPR08MB2878.namprd08.prod.outlook.com> (raw)
In-Reply-To: <DM8PR12MB54944A4FEC353FB2024D6571CDE29@DM8PR12MB5494.namprd12.prod.outlook.com>

Hi Asaf,



Please see details, let me know if more details required.

What DPDK version do you use?

DPDK-20.05

What EAL and devargs value are being used?

Following are the argv at eal_init

1005              if (rte_eal_init(argc, argv) < 0)

(gdb) p argv

$7 = {0x72bce60 "fast_pkt_app", 0x72bce90 "-c 6c", 0x72bcec0 "-m 1024", 0x72bcef0 "-n 1", 0x72bcf20 "--file-prefix=gnb_du_rte_config", 0x72bcf50 "--proc-type=auto", 0x72bcf80 "-w0000:c1:00.0",

  0x72bcfb0 "-w0000:c1:00.1", 0x72bcfe0 "", 0x72bd010 ""}

(gdb)



Regards,

Balbeer



-----Original Message-----
From: Asaf Penso <asafp@nvidia.com>
Sent: Tuesday, July 20, 2021 8:03 PM
To: Balbeer Tiwari <Balbeer.Tiwari@radisys.com>; dev@dpdk.org
Subject: RE: [dpdk-dev] DPDK Packet drop/Out of sequence issue with Jumbo frames on MLX ConnectX-4 Lx NIC



The e-mail below is from an external source. Please do not open attachments or click links from an unknown or suspicious origin.



Hello Balbeer,



Can you please provide more details?

What DPDK version do you use?

What EAL and devargs value are being used?



Regards,

Asaf Penso



>-----Original Message-----

>From: dev <dev-bounces@dpdk.org<mailto:dev-bounces@dpdk.org>> On Behalf Of Balbeer Tiwari

>Sent: Tuesday, July 20, 2021 4:54 PM

>To: dev@dpdk.org<mailto:dev@dpdk.org>

>Subject: [dpdk-dev] DPDK Packet drop/Out of sequence issue with Jumbo

>frames on MLX ConnectX-4 Lx NIC

>

>Hi There,

>

>I am using MLX ConnectX-4 Lx with DPDK and with this I am observing

>packet drops at receiver if size greater than ~8k(jumbo) frames.

>Smaller packets go through fine. Its being run directly on baremetal

>with Centos 8.3.  Please can you share if there is any fix for this.

>

>Regards,

>Balbeer

  reply	other threads:[~2021-07-20 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 13:54 Balbeer Tiwari
2021-07-20 14:32 ` Asaf Penso
2021-07-20 15:17   ` Balbeer Tiwari [this message]
2021-07-22 20:08     ` Asaf Penso

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=MWHPR08MB28783212FB478930E8E60E0293E29@MWHPR08MB2878.namprd08.prod.outlook.com \
    --to=balbeer.tiwari@radisys.com \
    --cc=asafp@nvidia.com \
    --cc=dev@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).