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 B1E6AC05027 for ; Mon, 6 Feb 2023 21:14:36 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 4C8D76B0075; Mon, 6 Feb 2023 16:14:36 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 479696B0078; Mon, 6 Feb 2023 16:14:36 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 31AA46B007D; Mon, 6 Feb 2023 16:14:36 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 215416B0075 for ; Mon, 6 Feb 2023 16:14:36 -0500 (EST) Received: from smtpin21.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id E5D51C070C for ; Mon, 6 Feb 2023 21:14:35 +0000 (UTC) X-FDA: 80438120910.21.D896A9C Received: from mail-pg1-f182.google.com (mail-pg1-f182.google.com [209.85.215.182]) by imf04.hostedemail.com (Postfix) with ESMTP id 0F6FC40019 for ; Mon, 6 Feb 2023 21:14:33 +0000 (UTC) Authentication-Results: imf04.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Q5VBT+2L; spf=pass (imf04.hostedemail.com: domain of htejun@gmail.com designates 209.85.215.182 as permitted sender) smtp.mailfrom=htejun@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=kernel.org (policy=none) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1675718074; h=from:from:sender: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=EOmjkak4hSmRchvmEJgN6IqY5BTXXjlVuAkqhp03RaU=; b=fxSaDsdm6QO2vd+FmjeENPffJvbPQDocQTN4TgaPqB8E31nDYwsT/YWEn0h1/XarEJCGZr 1+sU+ElOnASO+Kybxug+sjT3xX6imnMjjVSTJIkeR752BLJQfsOeJfeqFJQsQ2qXqMrt0q N3AeO2cVAj3TgvKpyeOEJiM+zuNbjww= ARC-Authentication-Results: i=1; imf04.hostedemail.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=Q5VBT+2L; spf=pass (imf04.hostedemail.com: domain of htejun@gmail.com designates 209.85.215.182 as permitted sender) smtp.mailfrom=htejun@gmail.com; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=kernel.org (policy=none) ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1675718074; a=rsa-sha256; cv=none; b=Ne9H7hz7ijzDPGQCoCDGM1vYPD4kDFKH55saRId4ZbWKQO0GHu2y5idrawxBQjO3H0Hv6e cWN38f6pggWY5fH0oVEKuM08MjiJQ34vef4nBVZY6SbWWiYPrzO/J81YaVzviv2EJOcfxe NDup+aGI0WoJrorHBe5QoBDXL5sTr+M= Received: by mail-pg1-f182.google.com with SMTP id v3so9106992pgh.4 for ; Mon, 06 Feb 2023 13:14:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:from:to:cc:subject:date:message-id :reply-to; bh=EOmjkak4hSmRchvmEJgN6IqY5BTXXjlVuAkqhp03RaU=; b=Q5VBT+2LKQxS9wiyf3Xi/Hm7NsRvScNG1exKySJO4Dq2OSUmrEmfapxLhGvnAj+nzj lIs5CgcCVS5i90KKIQDoyqNgoIhyL/L16hvRw+RHgrv8d0OuvPx2RucHIaT6yM3eeI6c VodL4y1qwpNmToerzPOBpI9hUs9WPe9VxU0AY0n5FjEY5lqGxPNXDE8SVCw8TqAECtt0 4Jwk2uo/SS/hCwspgO7ijlzCfuWtcM16cBVAqg8W72f7DguU3s5ZYlTBHALexjIcU+jV vHZv/KMeqeQiRVHoToYdVOBy2maKr2y4PsNiIcD8qcXTG1sC1F1l4/mm5VckTwB7eo9k dkUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:sender:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=EOmjkak4hSmRchvmEJgN6IqY5BTXXjlVuAkqhp03RaU=; b=GudDaa1KNkyVvOuplyHslBd6q4cBm9eTPEyOIDFw9x05BUOyT9vPbrWUnzoTOM6UO8 nHiC3wx2AzvGftxupEklL6p58sROkgUYMxQrOmJcbUfsaT9MkDzpy1lQjMfDlBNgcbSc fXD0SSYi6Vpv4yhrwT+fa8GSAMJtzjC9+jrij7NFWXLgDP3WL9tY07MeyXw3GlBQHvmY ytG4qfE5xuo5XFn3xaCfgGjplZJDS3tr3nHg6Y+f9A6QxZdl3TT95wQvx4w5gyuEUPlr 1XaALPfYz/STAjSwyVWfQz7wk8NirQfaxaFm+kXYDjJWvD1ppooDeqjykmW708quRXR2 Koww== X-Gm-Message-State: AO0yUKUImwgzJldT5vXCQzQgCXbMEy2sEa3RkJVldt10X9441X9KOZpZ 1MIESgj1X9fq65WmVfb2eI4= X-Google-Smtp-Source: AK7set8HpHmnm5AI0DRSN+d/xw18SaK99JMMN2/w+YbIW1MBZ0n52zMJqXaqJL5jC5vyocknwWbdBQ== X-Received: by 2002:a62:8412:0:b0:592:3eeb:51d9 with SMTP id k18-20020a628412000000b005923eeb51d9mr979165pfd.21.1675718072596; Mon, 06 Feb 2023 13:14:32 -0800 (PST) Received: from localhost (2603-800c-1a02-1bae-a7fa-157f-969a-4cde.res6.spectrum.com. [2603:800c:1a02:1bae:a7fa:157f:969a:4cde]) by smtp.gmail.com with ESMTPSA id d198-20020a621dcf000000b00593225b379dsm7613137pfd.106.2023.02.06.13.14.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Feb 2023 13:14:31 -0800 (PST) Date: Mon, 6 Feb 2023 11:14:30 -1000 From: Tejun Heo To: Alistair Popple Cc: linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, jgg@nvidia.com, jhubbard@nvidia.com, tjmercier@google.com, hannes@cmpxchg.org, surenb@google.com, mkoutny@suse.com, daniel@ffwll.ch, "Daniel P . Berrange" , Alex Williamson , Zefan Li , Andrew Morton Subject: Re: [PATCH 14/19] mm: Introduce a cgroup for pinned memory Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspam-User: X-Rspamd-Server: rspam03 X-Stat-Signature: enzsnzyq1s4rqfityukseehwyo3cgiga X-Rspamd-Queue-Id: 0F6FC40019 X-HE-Tag: 1675718073-197619 X-HE-Meta: U2FsdGVkX1+ZCGaB/LgzKf5lQNKIydtLKuJaSEu8YZbSjFTDf8s2+F6teDA2i7a5jgs4f0MFkqRB/f5VSbvSbL7/78a4RgfCiskw5beot1rgq/90klKwp3Xo00LpQX9Ca9oPNMVROEuMMBRtR49LctcbpHbdgUgJcefONwkAjvPRTboSbFZ0HJ6YB8SfG9nTj9dNulkK4SVXl+lxk/pcFMnGlpw85ho1C6ei8zX69kcMWlSnhSindvuZNVCyrEs+X8bkz+XPgB1QxFKuZd8NjP7+0tm1WNS0jsex0D8gFKLjbi4ckyyBG3fXqrt6hmxYfqlxDdk4O2Jw+lkygmobCjAqJKguYriabiji3GtuhSF3S5P4EucMhLCgGAdSjSMjHkDRoEoWTkXFK48x6PguK9c3XQK3FkX19NTBQdwPmBYEeqhDk+5KIS9SMw/zHjqHQlB99th64jO57hNzxTOCTlYNDV/7h09Z7DfomQ2jUv2hs83DfAhOF1WZ4ltjwDGAAO6M7FrMXQJXjqvDCNHe+AsyOARGxwfkJpXjWkj9wuMnODEkFVxCmafx+s5UrmVOPxxAB2wis15JvN2EgeUXuFb6XDa3Pu1VE31lVcqeiIDSW7qaQFdb8pTnnB2KqtyQdadwEHtJK33eatAjkfOWFz4P5hI9KDuk5oWWMDOzny7zcolmDSVpg/R2uDpIHYxLKwrERi1g2JpUd/JjF2uBPyJBTECLBUWVvC2OVfQ21BK0i3pO1Gg89lKeouY380ULSP/68vcN5iMODuBuO00+hgXRCqeD05zdgNYbTSmgdRzogkIQxp2mpNqXSjNq4w3KZUw4nfgfdLEZot9DA8mEBxWpZvm9UorNL2aCg9L6HV/jwo/kedOVs2GNidD32xgaH+PQ8E3yw4U3KPJHFn5zUhmkvbXcqRvhGmnZMSK7Asx0IdK9lvpLG+CzfYVbPSSS2ff0q2TPlEmN+JdgAJX XBdey2w1 fp283FcoT+ZDm5slf11RpSuzTpEUxkQNRRxyAkd8qgonvL4oHI+7IjAsAKLXY1RLqt44ljYh7gsSHfdWjTNKrIzGd7b+z78QC1uEj5yv6JD3z5y5o+z18trRdpuq55bDrMM3d6z7ZQaHIEtnAbap8Puy9EE3SS6qYGFA2TYJNi9/FnhT4MWILlYJku9rYXbI4HLhWvbptEXRJA8BqhhiH2X86sJ5qEFhRDZXnPCUYbLrh/bUMS028p7UktpPCBeFr6GExqrZCrlEBzonus3+KrYzL+vBub+0eLWHlvCUNHSp18ugTwT9sZRhG7Q3OUtLyH2i1CUiOeiHrW5Muv0+JySMZHTyIYAa9YiVBhivv7V/wFPPGoFiIb0GKP90xzfe61bbNOKOL5JJsZ/u5swnFEMbzZbHlJo5mH+L15YEiXhCD0Q4n6kzT227i8+4NcsH9sOB9e2cGDrNLEiLuCE+PoIeXTfPypsW8l+/MfcqISAJ8tchDOoCiy6IOwg== 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 Mon, Feb 06, 2023 at 06:47:51PM +1100, Alistair Popple wrote: > If too much memory in a system is pinned or locked it can lead to > problems such as performance degradation or in the worst case > out-of-memory errors as such memory cannot be moved or paged out. > > In order to prevent users without CAP_IPC_LOCK from causing these > issues the amount of memory that can be pinned is typically limited by > RLIMIT_MEMLOCK. However this is inflexible as limits can't be shared > between tasks and the enforcement of these limits is inconsistent > between in-kernel users of pinned memory such as mlock() and device > drivers which may also pin pages with pin_user_pages(). > > To allow for a single limit to be set introduce a cgroup controller > which can be used to limit the number of pages being pinned by all > tasks in the cgroup. As I wrote before, I think this might fit better as a part of memcg than as its own controller. Thanks. -- tejun