From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bruce.richardson@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 55C2B68A2
 for <dev@dpdk.org>; Fri, 14 Mar 2014 12:47:58 +0100 (CET)
Received: from orsmga002.jf.intel.com ([10.7.209.21])
 by orsmga101.jf.intel.com with ESMTP; 14 Mar 2014 04:49:28 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.97,654,1389772800"; d="scan'208";a="499810126"
Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155])
 by orsmga002.jf.intel.com with ESMTP; 14 Mar 2014 04:49:19 -0700
Received: from irsmsx153.ger.corp.intel.com (163.33.192.75) by
 IRSMSX102.ger.corp.intel.com (163.33.3.155) with Microsoft SMTP Server (TLS)
 id 14.3.123.3; Fri, 14 Mar 2014 11:49:16 +0000
Received: from irsmsx103.ger.corp.intel.com ([169.254.3.27]) by
 IRSMSX153.ger.corp.intel.com ([169.254.9.144]) with mapi id 14.03.0123.003;
 Fri, 14 Mar 2014 11:49:16 +0000
From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: sabu kurian <sabu2kurian@gmail.com>
Thread-Topic: [dpdk-dev] Packet crafting....
Thread-Index: AQHPP2hUbAIFcBny4k6YxtDmOL10iJrgVz8wgAAE0YCAAA1t4IAAC2eAgAACVDA=
Date: Fri, 14 Mar 2014 11:49:16 +0000
Message-ID: <59AF69C657FD0841A61C55336867B5B01A9C4588@IRSMSX103.ger.corp.intel.com>
References: <CAJ2bnfDNNGkWW01TmHeWY370diEhCTPJb8aP+EKB5xB71tL3aA@mail.gmail.com>
 <59AF69C657FD0841A61C55336867B5B01A9C4436@IRSMSX103.ger.corp.intel.com>
 <CAJ2bnfA8a3_uwiQD5ZxFT9pU-0cv0RB4qRdTfY3xZt_TbcgAfA@mail.gmail.com>
 <59AF69C657FD0841A61C55336867B5B01A9C452F@IRSMSX103.ger.corp.intel.com>
 <CAJ2bnfBgJiGQ+VumJY6f6R8ecmvEnQ4D24TyiXWmBwQxR6jZJg@mail.gmail.com>
In-Reply-To: <CAJ2bnfBgJiGQ+VumJY6f6R8ecmvEnQ4D24TyiXWmBwQxR6jZJg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [163.33.239.181]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Packet crafting....
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Mar 2014 11:47:58 -0000


> From: sabu kurian [mailto:sabu2kurian@gmail.com]=20
> Sent: Friday, March 14, 2014 11:38 AM
> To: Richardson, Bruce
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] Packet crafting....
>=20
> Thanks on the reply Richardson. You did mention something like "Don't for=
get that when you get the mbuf from=20
> rte_pktmbuf_alloc, you also need to set the length value to the appropria=
te size." .
>
>=A0Like I'm allocating the mbuf using rte_mbuf . The=A0rte_mempool_create =
has already set the maximum packet size=20
> for a mbuf and the number of mbuf's and all. So do I really need to use=
=A0rte_pktmbuf_alloc ?

How are you getting an mbuf from the pool, if not using rte_pktmbuf_alloc?
When you have an mbuf, that buffer has a maximum size, generally around 2k.=
 However, the packet inside that buffer is generally smaller than the overa=
ll buffer size and you must configure that size, otherwise the PMD, and the=
refore the NIC, has no idea how much data out of that 2k buffer needs to be=
 transmitted.