From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [RFC v2 00/23] Dynamic memory allocation for DPDK Date: Tue, 19 Dec 2017 07:46:35 -0800 Message-ID: <20171219074635.6c4f656d@xeon-e3> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, andras.kovacs@ericsson.com, laszlo.vadkeri@ericsson.com, keith.wiles@intel.com, benjamin.walker@intel.com, bruce.richardson@intel.com, thomas@monjalon.net To: Anatoly Burakov Return-path: Received: from mail-pl0-f65.google.com (mail-pl0-f65.google.com [209.85.160.65]) by dpdk.org (Postfix) with ESMTP id D8114160 for ; Tue, 19 Dec 2017 16:46:37 +0100 (CET) Received: by mail-pl0-f65.google.com with SMTP id i6so7183581plt.13 for ; Tue, 19 Dec 2017 07:46:37 -0800 (PST) In-Reply-To: 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 Tue, 19 Dec 2017 11:14:27 +0000 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. What exact functionality is this patchset trying to enable. It isn't clear what is broken now. Is it a cleanup or something that is being motivated by memory layout issues?