From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <olivier.matz@6wind.com>
Received: from mail-wr0-f180.google.com (mail-wr0-f180.google.com
 [209.85.128.180]) by dpdk.org (Postfix) with ESMTP id A1BE72C5
 for <dev@dpdk.org>; Tue, 18 Apr 2017 15:02:39 +0200 (CEST)
Received: by mail-wr0-f180.google.com with SMTP id c55so102053823wrc.3
 for <dev@dpdk.org>; Tue, 18 Apr 2017 06:02:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=6wind-com.20150623.gappssmtp.com; s=20150623;
 h=date:from:to:cc:subject:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding;
 bh=oMua53n7uChb01b2YLk/S5TwknEz2YPF31bQWfeTjQU=;
 b=necr7FO4fk9EzKpp8fa5lgvXYpn8YIwJgxywgOxL95MQNuUSnpzMc+/bpdzo4hEvYm
 LfYB3bxv5FO7mzaF9CF6OJOYHqeBJ2Io/MLGRrEArO/yd7iCAYwhDMxmF02bBJ8j3trQ
 uLRPpIRNaUoKODsZX2x9Pp6R6pZElNDqKV4vrnt0LGoFgknP/yjQ7GVrXMjQTuWtJhwx
 8xrNu6AQBxq6e/YbZmrhPK/j7C9Cer+4oSQsqctRFqXYVDQSwU55PG0yT47hQWqf7y2p
 Eefr3glAGJeXHH76ZArPgqMQgv0ANUvAidIB5A8lEuHk515JzEbjCYA9FmvT47LgsL5Y
 OaQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-transfer-encoding;
 bh=oMua53n7uChb01b2YLk/S5TwknEz2YPF31bQWfeTjQU=;
 b=SDWYiSiAiHeVtugv+oM6MS3vIiQMQZicdhiIdQo40eYTK5rX3X1c/Lfco3zc0oW9Ak
 Kae1g1V7898EavV6PyqfXKHm6g6ge1XfzZB+VBdCH2xfHVBBOpg0wae7Nn7O3+08tXRk
 pt4QStF+UPoif5Vj++zpH3bqS0e/5vaU5g5CsuQomsm6IG3JKeBeFxP0ranSko7ECoAy
 k97IcxmXtKYVwbRNCvFMcScp8suvzmLXr5u8IRCEyBEKR5tq0OWuhzC0Du1jnh5N1yzd
 FYoj+8Re//YlqDCgwxHLXlNIBx/dRu86IPiJmTj7Ju2jreLM3kai/5x0gcxJwCSYju0S
 fRCg==
X-Gm-Message-State: AN3rC/5cx8evvzcY8XCCZ04Tr8uC0nh9y9lIcbCVj0/D7zuNzSVY4PaR
 d6kmPv7BtGJhkx2qDpU=
X-Received: by 10.223.134.145 with SMTP id 17mr24601545wrx.130.1492520559371; 
 Tue, 18 Apr 2017 06:02:39 -0700 (PDT)
Received: from glumotte.dev.6wind.com (host.78.145.23.62.rev.coltfrance.com.
 [62.23.145.78])
 by smtp.gmail.com with ESMTPSA id u145sm14890232wmu.1.2017.04.18.06.02.39
 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
 Tue, 18 Apr 2017 06:02:39 -0700 (PDT)
Date: Tue, 18 Apr 2017 15:03:04 +0200
From: Olivier MATZ <olivier.matz@6wind.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: dev@dpdk.org, konstantin.ananyev@intel.com, bruce.richardson@intel.com,
 mb@smartsharesystems.com, andrey.chilikin@intel.com, jblunck@infradead.org,
 nelio.laranjeiro@6wind.com, arybchenko@solarflare.com,
 thomas.monjalon@6wind.com, jerin.jacob@caviumnetworks.com
Message-ID: <20170418150304.58d2c4a1@glumotte.dev.6wind.com>
In-Reply-To: <20170406054523.GP18844@yliu-dev.sh.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>
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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, 18 Apr 2017 13:02:39 -0000

Hi Yuanhan,

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

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?).

I'll do the change and send a rfc.

Regards,
Olivier