From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier MATZ Subject: Re: [PATCH] mk: link ring mempool by default for app build Date: Tue, 18 Apr 2017 14:04:08 +0200 Message-ID: <20170418140408.69df3672@glumotte.dev.6wind.com> References: <1492074127-24339-1-git-send-email-shreyansh.jain@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: , , , To: Shreyansh Jain Return-path: Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by dpdk.org (Postfix) with ESMTP id 197CDF94 for ; Tue, 18 Apr 2017 14:03:41 +0200 (CEST) Received: by mail-wm0-f45.google.com with SMTP id r190so12662635wme.1 for ; Tue, 18 Apr 2017 05:03:41 -0700 (PDT) In-Reply-To: <1492074127-24339-1-git-send-email-shreyansh.jain@nxp.com> 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 Thu, 13 Apr 2017 14:32:07 +0530, Shreyansh Jain wrote: > Signed-off-by: Shreyansh Jain Fixes: 9a8e9b57f544 ("mempool: move ring handler as a driver") Acked-by: Olivier Matz > --- > Context: > From the discussion in [1], it was observed that application should > have a default pool already linked even in case of shared builds. > Ring is especially important because packet mbuf creation API refer to > ring_mp_mc as default handler. > > Documentation for this is pending. > > [1] http://dpdk.org/ml/archives/dev/2017-April/063819.html Maybe this comment could go in the patch. Thanks, Olivier