From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal: add option to limit memory allocation on sockets Date: Fri, 13 Jul 2018 11:38:04 +0200 Message-ID: <2170003.TepNNdtj1D@xps> References: <2d97a30636fdaece6f64eabb597f2f892e3e93ad.1527787910.git.anatoly.burakov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, John McNamara , Marko Kovacevic To: Anatoly Burakov Return-path: Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by dpdk.org (Postfix) with ESMTP id A64A74CA5 for ; Fri, 13 Jul 2018 11:38:08 +0200 (CEST) In-Reply-To: <2d97a30636fdaece6f64eabb597f2f892e3e93ad.1527787910.git.anatoly.burakov@intel.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" 31/05/2018 19:35, Anatoly Burakov: > Previously, it was possible to limit maximum amount of memory > allowed for allocation by creating validator callbacks. Although a > powerful tool, it's a bit of a hassle and requires modifying the > application for it to work with DPDK example applications. > > Fix this by adding a new parameter "--socket-limit", with syntax > similar to "--socket-mem", which would set per-socket memory > allocation limits, and set up a default validator callback to deny > all allocations above the limit. > > This option is incompatible with legacy mode, as validator callbacks > are not supported there. > > Signed-off-by: Anatoly Burakov Applied, thanks