From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <olivier.matz@6wind.com>
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com
 [209.85.212.182]) by dpdk.org (Postfix) with ESMTP id 58468AFD8
 for <dev@dpdk.org>; Wed,  7 May 2014 17:37:44 +0200 (CEST)
Received: by mail-wi0-f182.google.com with SMTP id r20so1569336wiv.9
 for <dev@dpdk.org>; Wed, 07 May 2014 08:37:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
 :subject:references:in-reply-to:content-type
 :content-transfer-encoding;
 bh=lk/Bl7uGxlXyejB6NvbclXsot4jrgI8mu5KvNR4H9+A=;
 b=KGxoV5icqYQrzeV3i236TaCXGS7qmOQN4Ue/O0nGm8Aj/bh2O4rBTVq/CxpoKIvq35
 HgkzdSDSQ256EP2MgBjz7BUObx54R9zekOp/WGu0g3F0X/nqXnBK6Mq+ogG+rvOwmbkD
 uW2F4Z8/UUV54M6x2QtAX8ZP30zYhhuVfSHLmKsEwpMPq6gNvzrL+1H1hy/0CI64JOQx
 ZVn1flase1lpn8tZrbtTkiilZ1wIgACDfM6cbLK/7xRo3fXAdwH++94/MvI6iwL87w0J
 btq+LZ4zPioCthfHXcxaoi3p2wlk50BlC9ybc0UINKW3MZB1cLwD34+8Da38+Z9FlGlK
 0PPA==
X-Gm-Message-State: ALoCoQmRwdCc31dxctOWJxvKrF6IiI/x7trXSi2JjgiDPN953kkaDPwDzEGxgJBTpyjZVpTOQR9Y
X-Received: by 10.180.106.194 with SMTP id gw2mr8061865wib.47.1399477070175;
 Wed, 07 May 2014 08:37:50 -0700 (PDT)
Received: from [10.16.0.195] (6wind.net2.nerim.net. [213.41.180.237])
 by mx.google.com with ESMTPSA id ch16sm2469216wjb.43.2014.05.07.08.37.48
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 07 May 2014 08:37:49 -0700 (PDT)
Message-ID: <536A534B.6030306@6wind.com>
Date: Wed, 07 May 2014 17:37:47 +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: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>, 
 "Venkatesan, Venky" <venky.venkatesan@intel.com>,
 Igor Ryzhov <iryzhov@arccn.ru>, "dev@dpdk.org" <dev@dpdk.org>
References: <5368A5E0.8090903@arccn.ru> <5369E6AF.4040402@arccn.ru>
 <536A1B5C.2010201@6wind.com>
 <1FD9B82B8BF2CF418D9A1000154491D9740A339F@ORSMSX102.amr.corp.intel.com>
 <536A4CB3.9000005@6wind.com>
 <2601191342CEEE43887BDE71AB9772580EFA401D@IRSMSX105.ger.corp.intel.com>
In-Reply-To: <2601191342CEEE43887BDE71AB9772580EFA401D@IRSMSX105.ger.corp.intel.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-dev] RTE Ring removing
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: Wed, 07 May 2014 15:37:44 -0000

Hi Konstantin,

On 05/07/2014 05:19 PM, Ananyev, Konstantin wrote:
> Just to clarify about mempool - I suppose you are talking about
> ability to place internal ring and mempool metadata inside externally
> allocated memory?

Yes, exactly.

> It is already possible to keep mempool elements inside externally
> allocated memory (rte_mempool_xmem_create()).

You are right, but I think the current API is a bit too complex.
For instance the function rte_mempool_xmem_create() has 15 arguments
which is probably too much.

Anyway, as soon as I'll have a patch to show, I'll send it to the
mailing list so we can discuss it.

Regards,
Olivier