From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 4B00F5697 for ; Wed, 7 Oct 2015 00:19:25 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga103.jf.intel.com with ESMTP; 06 Oct 2015 15:19:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,646,1437462000"; d="scan'208";a="805115222" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga001.fm.intel.com with ESMTP; 06 Oct 2015 15:19:24 -0700 Received: from fmsmsx114.amr.corp.intel.com (10.18.116.8) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 6 Oct 2015 15:19:24 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.209]) by FMSMSX114.amr.corp.intel.com ([10.18.116.8]) with mapi id 14.03.0248.002; Tue, 6 Oct 2015 15:19:23 -0700 From: "Wiles, Keith" To: "hyunseok@ieee.org" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Jumbo frame support in pktgen Thread-Index: AQHRAINrFsi4xl9uV0a5cj12zVwdJZ5fjy0A Date: Tue, 6 Oct 2015 22:19:23 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.2.136] Content-Type: text/plain; charset="Windows-1252" Content-ID: <3A8D2A7ECE045A409E1EEFB8C2DA9BFC@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Jumbo frame support in pktgen X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2015 22:19:25 -0000 On 10/6/15, 11:07 PM, "dev on behalf of Hyunseok" wrote: >Hi, > >Can we generate 9k jumbo frames using the latest pktgen? Internally I do not create mbufs larger then 2K at this time in Pktgen. I guess it could be changed, but I do not have the time. If you want to submit a patch that would be great. > >Thanks! >-hs =8B=20 Regards, ++Keith Wiles Intel Corporation