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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1F432C433EF for ; Wed, 17 Nov 2021 08:23:32 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id BF21F61507 for ; Wed, 17 Nov 2021 08:23:31 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org BF21F61507 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=cmpwn.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id 510196B0072; Wed, 17 Nov 2021 03:23:21 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 498F86B0073; Wed, 17 Nov 2021 03:23:21 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3397E6B0074; Wed, 17 Nov 2021 03:23:21 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0222.hostedemail.com [216.40.44.222]) by kanga.kvack.org (Postfix) with ESMTP id 204F26B0072 for ; Wed, 17 Nov 2021 03:23:21 -0500 (EST) Received: from smtpin03.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id C4EC87F15C for ; Wed, 17 Nov 2021 08:23:10 +0000 (UTC) X-FDA: 78817732140.03.4B85AD6 Received: from out2.migadu.com (out2.migadu.com [188.165.223.204]) by imf14.hostedemail.com (Postfix) with ESMTP id 50724600199C for ; Wed, 17 Nov 2021 08:23:09 +0000 (UTC) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpwn.com; s=key1; t=1637137387; h=from:from: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:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BSRVikFW+PtuaMJ8jR31T42CGK4h9hlbjbP7fMd5tsY=; b=pE+RmDQ5yxDXkJ04CzwDyD3ULKlPJMyiZvdma6M2k95dKX8HCCaX0U6ejdF0MfoTWK3ZNp 6NlQkL0eUQvunYsiQwYnl4pWD//SWgN8jPnYR4WPlIBKJGRT8Xk8E14MDp0PTI/oo6HqYV ez/P9v9pXCV683l4zXAakhnG+9FRGlpGM45Kk49injCn8P7JYf0+myB0l4fa67IhJJ7OkY NFbA/a7B46CisVuAeO5vcGTLty/KUKy4GCr1RsyqQomkuaGI9GLxRr3Dh1VSfoALTpwyae iQEoBBdAhXIECB5bgo1ljoYZ8KEndVEzdYIxW8fqiQ2jcb16seQbgasBepTuzw== Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Wed, 17 Nov 2021 09:23:07 +0100 Message-Id: Cc: "Ammar Faizi" , , , "io_uring Mailing List" , "Jens Axboe" , "Pavel Begunkov" , Subject: Re: [PATCH] Increase default MLOCK_LIMIT to 8 MiB X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Drew DeVault" To: "Andrew Morton" References: <20211028080813.15966-1-sir@cmpwn.com> <593aea3b-e4a4-65ce-0eda-cb3885ff81cd@gnuweeb.org> <20211115203530.62ff33fdae14927b48ef6e5f@linux-foundation.org> <20211116114727.601021d0763be1f1efe2a6f9@linux-foundation.org> <20211116133750.0f625f73a1e4843daf13b8f7@linux-foundation.org> In-Reply-To: <20211116133750.0f625f73a1e4843daf13b8f7@linux-foundation.org> X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: 50724600199C X-Stat-Signature: xpbeahm4kjdfcp4b3gyg7fx4cy69jnap Authentication-Results: imf14.hostedemail.com; dkim=temperror ("DNS error when getting key") header.d=cmpwn.com header.s=key1 header.b=pE+RmDQ5; dmarc=temperror reason="SPF/DKIM temp error" header.from=cmpwn.com (policy=temperror); spf=temperror (imf14.hostedemail.com: error in processing during lookup of sir@cmpwn.com: DNS error) smtp.mailfrom=sir@cmpwn.com X-HE-Tag: 1637137389-686818 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: On Tue Nov 16, 2021 at 10:37 PM CET, Andrew Morton wrote: > We're never going to get this right, are we? The only person who can > decide on a system's appropriate setting is the operator of that > system. Haphazardly increasing the limit every few years mainly > reduces incentive for people to get this right. > > And people who test their software on 5.17 kernels will later find that > it doesn't work on 5.16 and earlier, so they still need to tell their > users to configure their systems appropriately. Until 5.16 is > obsolete, by which time we're looking at increasing the default again. > > I don't see how this change gets us closer to the desired state: > getting distros and their users to configure their systems > appropriately. Perfect is the enemy of good. This is a very simple change we can make to improve the status quo, and I think that's worth doing. I do not have time to develop a more sophisticated solution which steers the defaults based on memory present, and I definitely don't have the time to petition every distro to configure a better default for their particular needs. This is the easiest way to get broad adoption for a better default.