From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 5D20C1FE for ; Tue, 15 Jul 2014 11:11:56 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 15 Jul 2014 02:12:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,664,1400050800"; d="scan'208";a="543506158" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by orsmga001.jf.intel.com with ESMTP; 15 Jul 2014 02:07:59 -0700 Received: from irsmsx152.ger.corp.intel.com (163.33.192.66) by IRSMSX103.ger.corp.intel.com (163.33.3.157) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 15 Jul 2014 10:07:51 +0100 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.76]) by IRSMSX152.ger.corp.intel.com ([169.254.6.25]) with mapi id 14.03.0123.003; Tue, 15 Jul 2014 10:07:51 +0100 From: "Ananyev, Konstantin" To: Olivier MATZ , "Richardson, Bruce" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Making space in mbuf data-structure Thread-Index: Ac+XFzceY+GkJCrySPOdN5NThUK1YwCrU3QAAZGglfA= Date: Tue, 15 Jul 2014 09:07:51 +0000 Message-ID: <2601191342CEEE43887BDE71AB97725821338121@IRSMSX105.ger.corp.intel.com> References: <59AF69C657FD0841A61C55336867B5B02CF13E32@IRSMSX103.ger.corp.intel.com> <53BA7422.9080706@6wind.com> In-Reply-To: <53BA7422.9080706@6wind.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Making space in mbuf data-structure 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, 15 Jul 2014 09:11:56 -0000 Hi Oliver, >=20 > As this change would impact the core of DPDK, I think it would be > interesting to list some representative use-cases in order to evaluate > the cost of each solution. This will also help for future modifications, > and could be included in a sort of non-regression test? >=20 I think this is a very good idea. Let's create a list of such test-cases. =20 Two obvious apps from our side would probably be: - test-pmd iofwd mode - l3fwd What else should we add here? Konstantin