From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 87CE1189; Fri, 13 Jul 2018 05:38:07 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 13 Jul 2018 05:38:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=qKdEwYu4W6Y0s+1fQd2vfDz76X 2Hcx6Xp1LRn/19BUc=; b=pmRmM4+eOXkwlIQEZQIjNBFoN/p9OWpmERkjmwl3Ns R0/+WuTyKsYFvjcs/0dJMXiVDx2i+rN9kDErZJR1y64QlVam5YQnCqsfi6AImEk+ UywRpiTYL8lyGotjab9hnLiB4JKTAxXWtzOm6uL6QTghKqTzzYSuHVhBM15Xbmku c= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=qKdEwY u4W6Y0s+1fQd2vfDz76X2Hcx6Xp1LRn/19BUc=; b=OmtRzED8EAQfagzqhoSqNF xLP/xWINBvDQV7w/xCnP6qko04DmJ3miMVG7oMyor3Hk1jwhMwvNmXq5C54Zn9y3 kZNZUkRsVkYNjyJMmok/+628FcLpdgxpo9cgrtNgWveLq3mBkyGvrkP9IIGPslLl DC6i7ZtQ41zmCZfoGdBuI0zd7UFcBFAamjrTANU25o55XESztspmkiOhNgs5igAo 1+ztvhLgAoKCxt2MaExZKWCADA6nh5KUD2Pl5dfItFUcf7IAMDm6/PbaHCnblmKL l4NfCQd3/AFVgP5bljimpKYWqxF8sqaes4UFVSa5Oe2obxq4RXu8HrPW8/5aAO8A == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 44358E4818; Fri, 13 Jul 2018 05:38:06 -0400 (EDT) From: Thomas Monjalon To: Anatoly Burakov Cc: dev@dpdk.org, John McNamara , Marko Kovacevic Date: Fri, 13 Jul 2018 11:38:04 +0200 Message-ID: <2170003.TepNNdtj1D@xps> In-Reply-To: <2d97a30636fdaece6f64eabb597f2f892e3e93ad.1527787910.git.anatoly.burakov@intel.com> References: <2d97a30636fdaece6f64eabb597f2f892e3e93ad.1527787910.git.anatoly.burakov@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] eal: add option to limit memory allocation on sockets 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: Fri, 13 Jul 2018 09:38:08 -0000 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