From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Burakov, Anatoly" Subject: Re: [PATCH 00/23] Dynamic memory allocation for DPDK Date: Tue, 19 Dec 2017 11:15:01 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: andras.kovacs@ericsson.com, laszlo.vadkeri@ericsson.com, keith.wiles@intel.com, benjamin.walker@intel.com, bruce.richardson@intel.com, thomas@monjalon.net To: dev@dpdk.org Return-path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 5E0B01B023 for ; Tue, 19 Dec 2017 12:15:04 +0100 (CET) In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 19-Dec-17 11:04 AM, Anatoly Burakov wrote: > This patchset introduces a prototype implementation of dynamic memory allocation > for DPDK. It is intended to start a conversation and build consensus on the best > way to implement this functionality. The patchset works well enough to pass all > unit tests, and to work with traffic forwarding, provided the device drivers are > adjusted to ensure contiguous memory allocation where it matters. > > The vast majority of changes are in the EAL and malloc, the external API > disruption is minimal: a new set of API's are added for contiguous memory > allocation (for rte_malloc and rte_memzone), and a few API additions in > rte_memory. Every other API change is internal to EAL, and all of the memory > allocation/freeing is handled through rte_malloc, with no externally visible > API changes, aside from a call to get physmem layout, which no longer makes > sense given that there are multiple memseg lists. My apologies, this patchset was sent erroneously. Please look at the version tagged as "RFC v2". -- Thanks, Anatoly