From mboxrd@z Thu Jan 1 00:00:00 1970 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) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Dec 2017 03:15:03 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,426,1508828400"; d="scan'208";a="4004587" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.237.220.115]) ([10.237.220.115]) by orsmga008.jf.intel.com with ESMTP; 19 Dec 2017 03:15:01 -0800 To: dev@dpdk.org Cc: andras.kovacs@ericsson.com, laszlo.vadkeri@ericsson.com, keith.wiles@intel.com, benjamin.walker@intel.com, bruce.richardson@intel.com, thomas@monjalon.net References: From: "Burakov, Anatoly" Message-ID: Date: Tue, 19 Dec 2017 11:15:01 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH 00/23] Dynamic memory allocation for DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2017 11:15:05 -0000 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