From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zhihong.wang@intel.com>
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
 by dpdk.org (Postfix) with ESMTP id 34A502935
 for <dev@dpdk.org>; Tue,  4 Jul 2017 09:54:27 +0200 (CEST)
Received: from orsmga002.jf.intel.com ([10.7.209.21])
 by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
 04 Jul 2017 00:54:26 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.40,307,1496127600"; d="scan'208";a="106840950"
Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202])
 by orsmga002.jf.intel.com with ESMTP; 04 Jul 2017 00:54:26 -0700
Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by
 fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS)
 id 14.3.319.2; Tue, 4 Jul 2017 00:54:26 -0700
Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.116]) by
 SHSMSX101.ccr.corp.intel.com ([169.254.1.197]) with mapi id 14.03.0319.002;
 Tue, 4 Jul 2017 15:54:23 +0800
From: "Wang, Zhihong" <zhihong.wang@intel.com>
To: Olivier MATZ <olivier.matz@6wind.com>, Yuanhan Liu
 <yuanhan.liu@linux.intel.com>
CC: "dev@dpdk.org" <dev@dpdk.org>, "Ananyev, Konstantin"
 <konstantin.ananyev@intel.com>, "Richardson, Bruce"
 <bruce.richardson@intel.com>, "mb@smartsharesystems.com"
 <mb@smartsharesystems.com>, "Chilikin, Andrey" <andrey.chilikin@intel.com>,
 "jblunck@infradead.org" <jblunck@infradead.org>, "nelio.laranjeiro@6wind.com"
 <nelio.laranjeiro@6wind.com>, "arybchenko@solarflare.com"
 <arybchenko@solarflare.com>, "thomas.monjalon@6wind.com"
 <thomas.monjalon@6wind.com>, "jerin.jacob@caviumnetworks.com"
 <jerin.jacob@caviumnetworks.com>
Thread-Topic: [dpdk-dev] [PATCH v2 6/8] mbuf: use 2 bytes for port and nb
 segments
Thread-Index: AQHSrWFJYCC72yvIjEeoiaq/lZeCW6G3URiAgBNWRACAeS4YUA==
Date: Tue, 4 Jul 2017 07:54:23 +0000
Message-ID: <8F6C2BD409508844A0EFC19955BE0941512B02B2@SHSMSX103.ccr.corp.intel.com>
References: <1488966121-22853-1-git-send-email-olivier.matz@6wind.com>
 <20170404162807.20157-1-olivier.matz@6wind.com>
 <20170404162807.20157-7-olivier.matz@6wind.com>
 <20170406054523.GP18844@yliu-dev.sh.intel.com>
 <20170418150304.58d2c4a1@glumotte.dev.6wind.com>
In-Reply-To: <20170418150304.58d2c4a1@glumotte.dev.6wind.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.239.127.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] [PATCH v2 6/8] mbuf: use 2 bytes for port and nb
 segments
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <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: Tue, 04 Jul 2017 07:54:28 -0000



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier MATZ
> Sent: Tuesday, April 18, 2017 9:03 PM
> To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
> Cc: dev@dpdk.org; Ananyev, Konstantin <konstantin.ananyev@intel.com>;
> Richardson, Bruce <bruce.richardson@intel.com>;
> mb@smartsharesystems.com; Chilikin, Andrey <andrey.chilikin@intel.com>;
> jblunck@infradead.org; nelio.laranjeiro@6wind.com;
> arybchenko@solarflare.com; thomas.monjalon@6wind.com;
> jerin.jacob@caviumnetworks.com
> Subject: Re: [dpdk-dev] [PATCH v2 6/8] mbuf: use 2 bytes for port and nb
> segments
>=20
> Hi Yuanhan,
>=20
> On Thu, 6 Apr 2017 13:45:23 +0800, Yuanhan Liu
> <yuanhan.liu@linux.intel.com> wrote:
> > Hi Olivier,
> >
> > On Tue, Apr 04, 2017 at 06:28:05PM +0200, Olivier Matz wrote:
> > > Change the size of m->port and m->nb_segs to 16 bits.
> >
> > But all the ethdev APIs are still using 8 bits. 16 bits won't really
> > take effect without updating those APIs. Any plans?
> >
> > 	--yliu
>=20
> Yes, there is some work in ethdev, drivers and in example apps to
> make the change effective. I think we could define a specific type for
> a port number, maybe rte_eth_port_num_t. Using this type could be a
> first step (for 17.08) before switching to 16 bits (17.11?).
>=20
> I'll do the change and send a rfc.

Ping ;) Is this still in your plan?

Thanks
Zhihong

>=20
> Regards,
> Olivier