From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from proxy.6wind.com (host.76.145.23.62.rev.coltfrance.com [62.23.145.76]) by dpdk.org (Postfix) with ESMTP id 4663C691A for ; Tue, 17 May 2016 15:56:45 +0200 (CEST) Received: from [10.16.0.195] (unknown [10.16.0.195]) by proxy.6wind.com (Postfix) with ESMTP id 749C127ED8; Tue, 17 May 2016 15:55:08 +0200 (CEST) To: Jan Viktorin , dev@dpdk.org References: <20160517143432.48e5a305@pcviktorin.fit.vutbr.cz> Cc: David Hunt , Thomas Monjalon From: Olivier MATZ Message-ID: <573B2310.60907@6wind.com> Date: Tue, 17 May 2016 15:56:32 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160517143432.48e5a305@pcviktorin.fit.vutbr.cz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] What is the status of mempool manager? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2016 13:56:45 -0000 Hi Jan, On 05/17/2016 02:34 PM, Jan Viktorin wrote: > Hello, > > I was trying to find out the status of the mempool rework and found > this 36-pieces long patch set: > > http://dpdk.org/ml/archives/dev/2016-April/037464.html > > (I failed to apply it to 16.04, 2.1.0, current HEAD.) It should be integrated soon, as there was no comment during some time. I'll send a new version that applies on head + minor cosmetic changes. > and some bits around: > > http://dpdk.org/ml/archives/dev/2016-May/038390.html I need to review this one, it's on my todo list. > http://dpdk.org/ml/archives/dev/2016-April/037509.html I think the code is ready to be integrated, but I was expecting some reactions on the v4, especially some precisions about the use cases and the needs. See in the link "Things that should still be discussed". > http://dpdk.org/ml/archives/dev/2016-April/037457.html It is integrated since today ;) > http://dpdk.org/ml/archives/dev/2016-April/036979.html Some comments have been done by Konstantin and myself, I think a new version will be submitted. It will be integrated in 16.07. > ...but I am confused. > > I am trying to find out how to write a custom memory pool based on > the uio_dmem_genirq driver. It provides DMA memory via the UIO API > (maps). > > If I have a PMD running of top of this UIO, I need to implement a > custom allocator that gets memory from the dev->mem_resource (with > the mappings preloaded from the UIO by EAL). > > This is related to the SoC infra as given here: > > http://dpdk.org/ml/archives/dev/2016-May/038486.html > > Any idea how to start with this? I think your feedback would be very valuable. The "external mempool manager" series allows to register new handler that replaces the internal ring storing the objects. It does not change the way the memory is allocated. The big patchset introduce new way of allocating memory used by memory pool (no need to be virtually contiguous anymore). You could throw an eye on rte_mempool_populate*() functions that populate a mempool with memory for storing the objects. I'm not sure I'm getting your exact needs. Do you need to populate a ring-based mempool with specific memory, retrieved from UIO API? Do you need to replace the default internal ring by something else? Do you need to access the mempool from the hardware? Regards, Olivier