From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2DC99C4707B for ; Thu, 18 Jan 2024 09:04:37 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id AA8876B0082; Thu, 18 Jan 2024 04:04:36 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id A58566B0083; Thu, 18 Jan 2024 04:04:36 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 96E006B0085; Thu, 18 Jan 2024 04:04:36 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id 8B4E16B0082 for ; Thu, 18 Jan 2024 04:04:36 -0500 (EST) Received: from smtpin06.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 6757C1C0D67 for ; Thu, 18 Jan 2024 09:04:36 +0000 (UTC) X-FDA: 81691846152.06.D3B0F86 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.223.130]) by imf08.hostedemail.com (Postfix) with ESMTP id 400C416001E for ; Thu, 18 Jan 2024 09:04:33 +0000 (UTC) Authentication-Results: imf08.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=q0utVZF0; dkim=pass header.d=suse.com header.s=susede1 header.b=lK5Ihehp; spf=pass (imf08.hostedemail.com: domain of mkoutny@suse.com designates 195.135.223.130 as permitted sender) smtp.mailfrom=mkoutny@suse.com; dmarc=pass (policy=quarantine) header.from=suse.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1705568674; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=Lx9tonMV0p2LmGJzOUVmxlBkhvvyPY8HKeuAJPQh4ks=; b=O+FGxVeV2zALjkCxm7dRn0nBmAzs2quu+M30T0LpwL1EHD8EuDdC5Vz9X+OB2+vTTNqhMH I+L4MkDRk6Tl3HUwodQePzvGJo36g36nqtpvbq/ysiq87pfYE//Xmxj/A2irBoXhvTZoaj l4BLWvuDtLsFXRTmRik9Wb8hKBGCx70= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1705568674; a=rsa-sha256; cv=none; b=vK+lzlbRdBQ+y2fU31cy7XYbHWIoWek1hoPaGbGqYfw6/uFUUDXHHTrVJ/Hu6ksAuL1f3p LVZ+y86De4Z5flSRm2stYGOfQ1Kt+xF9hTv/xWGKzpWrMwnnYO2vgmhcJMtFJuQXPmsgkG Nvjx95ZuVE31+pDWjK7Niozk9PayBg8= ARC-Authentication-Results: i=1; imf08.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=q0utVZF0; dkim=pass header.d=suse.com header.s=susede1 header.b=lK5Ihehp; spf=pass (imf08.hostedemail.com: domain of mkoutny@suse.com designates 195.135.223.130 as permitted sender) smtp.mailfrom=mkoutny@suse.com; dmarc=pass (policy=quarantine) header.from=suse.com Received: from imap1.dmz-prg2.suse.org (imap1.dmz-prg2.suse.org [IPv6:2a07:de40:b281:104:10:150:64:97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 4FA5922049; Thu, 18 Jan 2024 09:04:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1705568672; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Lx9tonMV0p2LmGJzOUVmxlBkhvvyPY8HKeuAJPQh4ks=; b=q0utVZF0O92nhdxl2kE4a6MZyKsKAtvwi2N/IkUkbVsotX2YQISspqe6TosRHNUqMz6vvd UMuwMgDMufs7dSmREmYrsR45+gZH1uOI5mW655ZZuwG2jbpRKj7+1wxZXy69NcoCfWoU51 qrMnarvLlmNUaTJEwYqtrWXp9d++Yew= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1705568671; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Lx9tonMV0p2LmGJzOUVmxlBkhvvyPY8HKeuAJPQh4ks=; b=lK5IhehpmssMnTKxdBPOWJ6FwenHO4AUxX3t+ItSvSa8aQd1liz32rxnFfsuF4P4mEVXmm x5N5wbY5N+SOGshCLSfORkSdYDJbvlOiTfwb0Q+su98rU52Qwz5S/b/9EF680lLKga9eTF uE2CvXGmtfCRkv5pLJThqB1Ki728rMA= Received: from imap1.dmz-prg2.suse.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by imap1.dmz-prg2.suse.org (Postfix) with ESMTPS id E026113874; Thu, 18 Jan 2024 09:04:30 +0000 (UTC) Received: from dovecot-director2.suse.de ([10.150.64.162]) by imap1.dmz-prg2.suse.org with ESMTPSA id PpbYNZ7pqGXBMQAAD6G6ig (envelope-from ); Thu, 18 Jan 2024 09:04:30 +0000 Date: Thu, 18 Jan 2024 10:04:29 +0100 From: Michal =?utf-8?Q?Koutn=C3=BD?= To: Josh Poimboeuf Cc: Linus Torvalds , Jeff Layton , Chuck Lever , Shakeel Butt , Roman Gushchin , Johannes Weiner , Michal Hocko , linux-kernel@vger.kernel.org, Jens Axboe , Tejun Heo , Vasily Averin , Waiman Long , Muchun Song , Jiri Kosina , cgroups@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH RFC 4/4] mitigations: Add flock cache accounting to 'mitigations=off' Message-ID: References: <3e803d5aee5dd1f4c738f0de1e839e6cfcb9dc41.1705507931.git.jpoimboe@kernel.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="u4b4gqso4ihknobk" Content-Disposition: inline In-Reply-To: <3e803d5aee5dd1f4c738f0de1e839e6cfcb9dc41.1705507931.git.jpoimboe@kernel.org> X-Rspamd-Queue-Id: 400C416001E X-Rspam-User: X-Stat-Signature: s8n9fo69hxtdiaewkkz38ehs798qhma4 X-Rspamd-Server: rspam03 X-HE-Tag: 1705568673-42771 X-HE-Meta: U2FsdGVkX18vaQjq3yOYNkf2+zVs+kvrBcEHHGbQ/Edkz5B79AKDiR9Jrh+yqwIjTFgiyUx+qwlmN/5bIFfofpe7BrUV+hPKrM6dwIinDMZcCFKistUlgOgoBiEOav2gJ6eSeGtgnfObLpmKJ3ILNUswmQRsqLhiuwAy/xDqiBv24HSnMm4PEExCw+F3U11IHdXpXhQ3knuq4cSmjRWXIHsfLJ0fXa2t65RA0ysTrlfD2kU8HOTqB6LINCHdKKCzE2l+nJmd+DRNnL1ipP2R6lcIYzq/wlkAMM9Fa6u/zkTXyfnwbe//74jQKzkMVectf2EmLA7bDRYAK6Bgts+PNUjERIC6yPM/8+3wIWEIg+JxvSjMu/8DAyJKzKd+60uvMa8gBO8ZAVQuZu4Ne4J7Xx4ulgxdzjis3vJvSkNIX9qgSMFaulfAVAg1LnTG6VhVPqKhRNWJ+31ts53WRLyfo8EeKyg9eksJ0v51Xkh/NDIx3a2ReQY1X3LWxry9w7QKHY3ZJRfMIRghTd0GK5zPDNYDhqPg/4yjbnjPVQxLgH80hsLw1dYkkkudLzb2fHz8ZiVXdOSbOmHBqqgZ+Oh6CHWB4BHhLQofA/EpjO80p6yslwgEQB/xcwXkEIAgjf4ObpKqZoIB0NW+oAPkLieSQGDyF9DhtTcWbhV4G6evzGaMzhyjtzE//nFNqpCgfjb22jZrSiNCev/sv3piU8ldEI9mr7xvBzG1s3jUFddUS5W/4ztzr0SX4lyYThODME2u3Yu9Aw1LOTVcHeLSOqpsFrW/08pgBt57o4jTn8JeeP4R48H16Gis37KpIp4UggABitEx6P2rTZGhmnq2fcGlZ2VJw8rh91PaURzC2EcI4EnuXDHvB30REw5CGJi1UkfLnNLLffvKZYZBjJ9kbnmNcLHf1weBPjHiOypCuEEbrT9t87/mOHPQpXSW02Raawa9ez6gsWA3bMM= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: --u4b4gqso4ihknobk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jan 17, 2024 at 08:14:46AM -0800, Josh Poimboeuf wrote: > Allow flock cache accounting to be disabled with 'mitigations=off', as > it fits the profile for that option: trusted user space combined with a > performance-impacting mitigation. Note that some other kernel objects that don't have any other tight limit are already charged too (but their charging likely did not stand out in any performance regression tests). In the situation you describe, users can already pass `cgroup.memory=nokmem` and get rid of charging overhead in general. IOW, if flock objects are charged, there already is a boot option to turn off such behavior. Regards, Michal --u4b4gqso4ihknobk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQQpEWyjXuwGT2dDBqAGvrMr/1gcjgUCZajpkQAKCRAGvrMr/1gc jnI1AQCbThmyZZHc0yb1sSU87kRYGU6A+8Qm5wtthTdtlNoPuwEAnOxavnxMkLvy VhsoAek+ajhMUjJp7v03BI1OEx2X/AA= =LaB0 -----END PGP SIGNATURE----- --u4b4gqso4ihknobk--