[dpdk-users] Too much data being sent with small packet and IXGBE

[dpdk-users] Too much data being sent with small packet and IXGBE

[terry.montague.1980]

Hi there,
I'm trying to send a single IGMP control packet out of an Intel X550 to its connected router.
I've looked at the packet in wireshark and its absolutely fine, the ethernet header, the ip header, the ipchecksum offload and the IGMP payload & checksum - there's nothing wrong with it.
It is 46 bytes formatted and the pkt and data lengths of the allocated buffer are all set to 46 bytes. Its a 46 byte packet - end of!
However....  what comes out of the interface is 60 bytes of data - the 46 bytes I want to send + 14 bytes of zeros.
The 14 bytes is curiously equivalent to the size of an ethernet header, but I just cannot see how it is just being added on to the end of the packet data.
Has anyone else observed this effect , or indeed know what's causing it ?
Many thanks
Terry.
From keith.wiles@intel.com  Mon Sep 10 22:39:20 2018
Return-Path: <keith.wiles@intel.com>
Received: from mga06.intel.com (mga06.intel.com [134.134.136.31])
 by dpdk.org (Postfix) with ESMTP id B382058FA
 for <users@dpdk.org>; Mon, 10 Sep 2018 22:39:19 +0200 (CEST)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga007.jf.intel.com ([10.7.209.58])
 by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
 10 Sep 2018 13:39:18 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.53,357,1531810800"; d="scan'208";a="71878948"
Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206])
 by orsmga007.jf.intel.com with ESMTP; 10 Sep 2018 13:39:17 -0700
Received: from fmsmsx118.amr.corp.intel.com (10.18.116.18) by
 FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS)
 id 14.3.319.2; Mon, 10 Sep 2018 13:39:17 -0700
Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.210]) by
 fmsmsx118.amr.corp.intel.com ([169.254.1.229]) with mapi id 14.03.0319.002;
 Mon, 10 Sep 2018 13:39:17 -0700
From: "Wiles, Keith" <keith.wiles@intel.com>
To: "terry.montague.1980@btinternet.com" <terry.montague.1980@btinternet.com>
CC: "users@dpdk.org" <users@dpdk.org>
Thread-Topic: [dpdk-users] Too much data being sent with small packet and IXGBE
Thread-Index: AQHUSTdFYua0UPViY0GbT5460tuaUaTqb5eA
Date: Mon, 10 Sep 2018 20:39:16 +0000
Message-ID: <BC731613-2D88-4584-8B70-37692735B95F@intel.com>
References: <9772948.50847.1536605469967.JavaMail.defaultUser@defaultHost>
In-Reply-To: <9772948.50847.1536605469967.JavaMail.defaultUser@defaultHost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.254.188.247]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A6AA4D961071DB49A750DDF4A19C3B29@intel.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-users] Too much data being sent with small packet and
 IXGBE
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2018 20:39:20 -0000



> On Sep 10, 2018, at 1:51 PM, terry.montague.1980@btinternet.com wrote:
>=20
> Hi there,
> I'm trying to send a single IGMP control packet out of an Intel X550 to i=
ts connected router.
> I've looked at the packet in wireshark and its absolutely fine, the ether=
net header, the ip header, the ipchecksum offload and the IGMP payload & ch=
ecksum - there's nothing wrong with it.
> It is 46 bytes formatted and the pkt and data lengths of the allocated bu=
ffer are all set to 46 bytes. Its a 46 byte packet - end of!
> However....  what comes out of the interface is 60 bytes of data - the 46=
 bytes I want to send + 14 bytes of zeros.
> The 14 bytes is curiously equivalent to the size of an ethernet header, b=
ut I just cannot see how it is just being added on to the end of the packet=
 data.
> Has anyone else observed this effect , or indeed know what's causing it ?

Not sure what you are doing, but the smallest packet on ethernet is 60 byte=
s + 4 bytes CRC for 64 bytes total. Normally anything less then 60 bytes + =
CRC is called a runt packet and are discarded. The NIC is padding the data =
to 60 bytes then adds the 4 byte CRC.

Hope that helps.

> Many thanks
> Terry.

Regards,
Keith