From nobody Mon Dec 11 19:13:01 2023 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sprx92mK8z53yd2 for ; Mon, 11 Dec 2023 19:13:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sprx90XW8z4cKB for ; Mon, 11 Dec 2023 19:13:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1702321981; a=rsa-sha256; cv=none; b=aaNzRSn4lYo1oC+yg3nLMAOi4zUtMUBPIxjv5MYSf1hPm+U5IW1zMmPfaqy+tElLOVX0md nsbudHpqRcTuseNLoMxGTqsbT4tW26NgGcUwGIpDE50+ZHYrBwMg61fsgKkpCqSFathiJF Ayeh7ebFbv5TwGrCSt4XDoPHJyKdDdB3HOLrkBb8oyteqCEAF+I42eQX5/3tEKdX21Q9fR PufB5DfID6jmyYpHN5C+vinG0lfih4MYKECIAthGrnjjUvWaWh6Alj5ZNIUXlFvQiVwlIm zrdQreSVKJYQ6mTCgmfwkWRSNDnd6if6diTXGBVeJaXvRUWiZ1NBRWXHug3ukA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1702321981; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FpjKSChznW+5LDJfdzGI+gDDx9zJa7iFyAiVNb/+ekM=; b=Z57Uj5+lRPyfWQPaBm/KbSEnJK0NdurHMfiUupiXv5WOmsXxIH3dcoxTQr2aJi7okdooMK BNnTwXRAMuBEqc0COLKz9oXHzPCDU+Q+gENFFWyyjet6GNDiaBwoNxA8zzkPzNzeRHWyvB A7M6n86BLoILeBRSqwN5NPmsh/oVEI+VTAL9lpVlBYvELpPohBd2BIT5DqfcFX2z/hoaAJ kWiqq1xynTR19zQX5O8VyJR8PFFWpCgSz2G5F3QVsb8yI8Cj6DjI8gOg+estAfzuMSEQAc daVDJJtyj1cj0Onc2rD+AIq5FwkkVq3IxYybk0pSENJB7SfiWxXKoju4UQmClw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Sprx86jrjzjWv for ; Mon, 11 Dec 2023 19:13:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 3BBJD0hl065945 for ; Mon, 11 Dec 2023 19:13:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3BBJD0e6065944 for bugs@FreeBSD.org; Mon, 11 Dec 2023 19:13:00 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275436] tmpfs does not honor memory limits on writes Date: Mon, 11 Dec 2023 19:13:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: karels@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275436 --- Comment #12 from Mike Karels --- (In reply to Konstantin Belousov from comment #11) > So what would happen if swap is added or removed? In theory the reserve should be increased or decreased, but that does not happen. However, the available space will be computed based on the new/cur= rent swap space available. > This cannot handle situation when a program allocates anon memory. Right, it knows nothing about competing memory demands. I'll run a few more experiments and see if anything better comes to mind. = If not, I'll put this into a review. --=20 You are receiving this mail because: You are the assignee for the bug.=