From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <olivier.matz@6wind.com>
Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67])
 by dpdk.org (Postfix) with ESMTP id 732355933
 for <dev@dpdk.org>; Mon, 12 May 2014 18:13:46 +0200 (CEST)
Received: from was59-1-82-226-113-214.fbx.proxad.net ([82.226.113.214]
 helo=[192.168.0.10])
 by mail.droids-corp.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128)
 (Exim 4.80) (envelope-from <olivier.matz@6wind.com>)
 id 1Wjssp-0000TX-Bc; Mon, 12 May 2014 18:15:31 +0200
Message-ID: <5370F326.8070206@6wind.com>
Date: Mon, 12 May 2014 18:13:26 +0200
From: Olivier MATZ <olivier.matz@6wind.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Icedove/24.4.0
MIME-Version: 1.0
To: Stephen Hemminger <stephen@networkplumber.org>
References: <1399647038-15095-1-git-send-email-olivier.matz@6wind.com>	<1399647038-15095-7-git-send-email-olivier.matz@6wind.com>	<3144526.CGFdr4BbI8@xps13>	<1FD9B82B8BF2CF418D9A1000154491D9740A92B8@ORSMSX102.amr.corp.intel.com>	<20140512144108.GB21298@hmsreliant.think-freely.org>	<5370E397.7000706@6wind.com>
 <20140512085924.20a29cad@nehalam.linuxnetplumber.net>
In-Reply-To: <20140512085924.20a29cad@nehalam.linuxnetplumber.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH RFC 06/11] mbuf: replace data pointer by an
 offset
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: Mon, 12 May 2014 16:13:46 -0000

Hi Stephen,

On 05/12/2014 05:59 PM, Stephen Hemminger wrote:
> There is one case which this case might make problematic.
> Right now it is possible to clone an mbuf and in the cloned mbuf
> use the associated data buffer as private meta data store.
> This is convenient (like skb->cb in Linux) and avoids addtional
> allocation.

I don't get your point. Why using rte_pktmbuf_mtod(m, char *)
wouldn't work in your case?