From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <olivier.matz@6wind.com>
Received: from mail-we0-f180.google.com (mail-we0-f180.google.com
 [74.125.82.180]) by dpdk.org (Postfix) with ESMTP id BA700AFD6
 for <dev@dpdk.org>; Wed,  7 May 2014 17:09:36 +0200 (CEST)
Received: by mail-we0-f180.google.com with SMTP id t61so1124557wes.25
 for <dev@dpdk.org>; Wed, 07 May 2014 08:09:42 -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=hJpAScez4Bnd9pAG2JmmzZ9ATiAzgLR/8DOUD1yyi9o=;
 b=jahVm3gwxaVw6sa3UW0YNwIKIiN958zFzx+h5qQeO2fXWl3WaU0kVO2ItpI9mZWqFB
 j0xHuEQPQUUSUnrfjzK3TUn8kbGze1/ogz3238awmYJJYugv/gn2+GqKIGATKZBZoLVi
 hHi33oaJVxcNgqEQI2OpwYJAVAIgwegcnrBW4QSiWM7e0fTNSCOV6tK9n5hxbJHEgoUn
 jqNxMjC59WB7kXuKQA1VntVZLoYMUJ6FVFZZEyZEsTVOv/iIfwiWrZXCjW7qm/QocM/b
 yhVUSSChm5vznlca+mamdNNKA7pfyiGfmDlOsh5+a8neeIDnJ+2Q6XhNLiqDWxE27LVS
 +v1w==
X-Gm-Message-State: ALoCoQkocaoC3GzZ9C4tVvZHWH+JBlPLBHnTmLojOw7gJwYPl7nIASOFq63aOJYxma1iYFyJQSFW
X-Received: by 10.180.84.129 with SMTP id z1mr8237908wiy.8.1399475382382;
 Wed, 07 May 2014 08:09:42 -0700 (PDT)
Received: from [10.16.0.195] (6wind.net2.nerim.net. [213.41.180.237])
 by mx.google.com with ESMTPSA id cg2sm2383982wjb.46.2014.05.07.08.09.40
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 07 May 2014 08:09:41 -0700 (PDT)
Message-ID: <536A4CB3.9000005@6wind.com>
Date: Wed, 07 May 2014 17:09:39 +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: "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>
In-Reply-To: <1FD9B82B8BF2CF418D9A1000154491D9740A339F@ORSMSX102.amr.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:09:37 -0000

Hi Venky,

On 05/07/2014 04:01 PM, Venkatesan, Venky wrote:
> We should look at how to make the memseg capable of doing alloc/free
> (including re-assembly of fragments) after the 1.7 release. Is that
> something you are considering doing (or are there any other DPDKers
> considering this), or should I look at putting together a patch for
> that?

No, that's not something I'm working on today.

On this topic, I have some work in progress in the rte_mempool code.
I'll submit it here as soon as it is ready, I'm not sure it will be
finished before the end of the 1.7.0 integration window.

Regards,
Olivier