From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=/p600Y77ynx0zDrbMzQ6XFxbK0ptubo1WMEZjUZG5B8=; b=RX/btwF0IxRfIXTQGYnxim/hxO3Zul6n6PRadigaB3W+n+FHBfdU56MUtBeF/4fhjZ HTFJxAwXVKTgl2s4OWQ6ewbslJztS4Ae6gdOL0P0pRRNY9jYu3pcmXOS72y6rEEC6t1L 8kudC/jCclJBfIsWvTDFdduL0xxneKx/IzOOgYdhquUjLCT0h3m2AQGTDYw2N6TeQ3hF pnEHTHuUcbUi0qc8LRmiZdvEwXgzFNKgIibEbkPBsRq4Q/x3Q42vC54TcLqrZ6LkrkR8 njdW4PZ2MDZaiAZPJAFnS7lFuPuDZw1piq+0FYnHuNDt+IbXLm+ki4LYE0exNZTwrb2I eptg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=/p600Y77ynx0zDrbMzQ6XFxbK0ptubo1WMEZjUZG5B8=; b=RQ4VZr67ZCkkL/qdvtt8emmXEoKXiJm6AtxPLqRnr07KNsTfUacd1WuJ1ZWhKwmQQj s92UCG/PLOlUtSmGAz9kSU7+1oBTdQL5ZE42pzbX9qwVhL5iWDyOLD9r9zx38i378xwT KZSW2Q+mRjyX0jcpuTGiwHG40DTARt3BC6Km1xXgHm640+lA53aj2lin7rK+UkPE9cZL zRTrgB9NfUzbLOh00mks1J/g/E4FTAhrTjwM5Cu7f+NWkA0srQeSxA3MD9wc3NrqBYNP 7DSZO3iPKrVMpttH1rgW9kw9D9Sw4zNiNpB+MvloSxm59Or6DiBqH758/rytmT0AYM+d e36w== X-Gm-Message-State: AKGB3mJ59Sp//XsLb/LIXkqsxN80PwwZ/XoKr6eghrX58Ev99VGPCk6g 5D7reK2uiqCcvI7OJ3w6CoGpg7hOBrI= X-Google-Smtp-Source: ACJfBos9l481W8cSYV2CBikSBD4pGKh0xNYsNKJB2tyPawdvz1yES38rG9GDCKHYPJCgWrh6fmH48Q== X-Received: by 10.159.231.19 with SMTP id w19mr3725693plq.45.1513698397076; Tue, 19 Dec 2017 07:46:37 -0800 (PST) Received: from xeon-e3 (204-195-18-133.wavecable.com. [204.195.18.133]) by smtp.gmail.com with ESMTPSA id x15sm27303092pfh.27.2017.12.19.07.46.36 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 19 Dec 2017 07:46:36 -0800 (PST) Date: Tue, 19 Dec 2017 07:46:35 -0800 From: Stephen Hemminger To: Anatoly Burakov 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 Message-ID: <20171219074635.6c4f656d@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [RFC v2 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 15:46:38 -0000 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?