From patchwork Mon Oct 24 19:05:49 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Stefan Roesch X-Patchwork-Id: 13017982 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 B7825C38A2D for ; Mon, 24 Oct 2022 19:06:27 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id AF8FA940008; Mon, 24 Oct 2022 15:06:26 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id AA950940007; Mon, 24 Oct 2022 15:06:26 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 9BF49940008; Mon, 24 Oct 2022 15:06:26 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 8915B940007 for ; Mon, 24 Oct 2022 15:06:26 -0400 (EDT) Received: from smtpin07.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 4A71E140AEF for ; Mon, 24 Oct 2022 19:06:26 +0000 (UTC) X-FDA: 80056773972.07.5C20522 Received: from 66-220-144-178.mail-mxout.facebook.com (66-220-144-178.mail-mxout.facebook.com [66.220.144.178]) by imf26.hostedemail.com (Postfix) with ESMTP id C9B0D14001D for ; Mon, 24 Oct 2022 19:06:24 +0000 (UTC) Received: by dev1180.prn1.facebook.com (Postfix, from userid 425415) id 447583ED5906; Mon, 24 Oct 2022 12:06:12 -0700 (PDT) From: Stefan Roesch To: kernel-team@fb.com, linux-block@vger.kernel.org, linux-mm@kvack.org Cc: shr@devkernel.io, axboe@kernel.dk, clm@meta.com, willy@infradead.org, hch@infradead.org Subject: [RFC PATCH v3 00/14] mm/block: add bdi sysfs knobs Date: Mon, 24 Oct 2022 12:05:49 -0700 Message-Id: <20221024190603.3987969-1-shr@devkernel.io> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1666638385; a=rsa-sha256; cv=none; b=Ts3fwUQZ3SlxpOb/rpfkeDENsPtPPTB7hlHS7/UZyrKwHd6n5pBhfm42f732P8dCw1YC+H mIaEW6qKj+A9n8qtibRScdspZrdxj+TKL0KBbQ9VW3CPSjNR9milEhILl16ov2mH7T+uaa wvIL9h7jxtIscyqTvZu7Gv86Ib9AkmM= ARC-Authentication-Results: i=1; imf26.hostedemail.com; dkim=none; dmarc=none; spf=neutral (imf26.hostedemail.com: 66.220.144.178 is neither permitted nor denied by domain of shr@devkernel.io) smtp.mailfrom=shr@devkernel.io ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1666638385; 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-transfer-encoding:content-transfer-encoding: in-reply-to:references; bh=as5o2mMQ8l7zQcL1t6Q+lbSn5FDsdCt6F3Q6SIId7y0=; b=tlSe5BbHLktWguBzcRRHyXR4fr7aQvWVNmlvV7HcafDz+h5vGt5XyYcGoKNSJXDmptQ68h sPuVv2az8FyBmUHK8cVpqPRUMhpedCtexh4mF9lU8Nmenf69isq/rmDEv3+/b7rDKJ6cpP 6ywZtF2nNeiZd8O7eEgRUilrZDNU8Ns= X-Stat-Signature: qd8cjt548a5zmk7a74aytrig73a4qowh X-Rspamd-Queue-Id: C9B0D14001D Authentication-Results: imf26.hostedemail.com; dkim=none; dmarc=none; spf=neutral (imf26.hostedemail.com: 66.220.144.178 is neither permitted nor denied by domain of shr@devkernel.io) smtp.mailfrom=shr@devkernel.io X-Rspam-User: X-Rspamd-Server: rspam05 X-HE-Tag: 1666638384-147353 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: At meta network block devices (nbd) are used to implement remote block storage. In testing and during production it has been observed that these network block devices can consume a huge portion of the dirty writeback cache and writeback can take a considerable time. To be able to give stricter limits, I'm proposing the following changes: 1) introduce strictlimit knob Currently the max_ratio knob exists to limit the dirty_memory. However this knob only applies once (dirty_ratio + dirty_background_ratio) / 2 has been reached. With the BDI_CAP_STRICTLIMIT flag, the max_ratio can be applied without reaching that limit. This change exposes that knob. This knob can also be useful for NFS, fuse filesystems and USB devices. 2) Use part of 1000 internal calculation The max_ratio is based on percentage. With the current machine sizes percentage values can be very high (1% of a 256GB main memory is already 2.5GB). This change uses part of 1000 instead of percentages for the internal calculations. 3) Introduce two new sysfs knobs: min_bytes and max_bytes. Currently all calculations are based on ratio, but for a user it often more convenient to specify a limit in bytes. The new knobs will not store bytes values, instead they will translate the byte value to a corresponding ratio. As the internal values are now part of 1000, the ratio is closer to the specified value. However the value should be more seen as an approximation as it can fluctuate over time. Changes: V3: - change signature of function bdi_ratio_from_pages to take an unsigned long parameter - use div64_u64 function for division to support 32 bit platforms - Refreshed to 6.1-rc2 V2: - Refreshed to 6.1-rc1 - Use part of 1000, instead of part of 10000 - Reformat cover letter *** BLURB HERE *** Stefan Roesch (14): mm: add bdi_set_strict_limit() function mm: add knob /sys/class/bdi//strict_limit mm: document /sys/class/bdi//strict_limit knob mm: use part per 1000 for bdi ratios. mm: add bdi_get_max_bytes() function mm: split off __bdi_set_max_ratio() function mm: add bdi_set_max_bytes() function. mm: add knob /sys/class/bdi//max_bytes mm: document /sys/class/bdi//max_bytes knob mm: add bdi_get_min_bytes() function. mm: split off __bdi_set_min_ratio() function mm: add bdi_set_min_bytes() function mm: add /sys/class/bdi//min_bytes knob mm: document /sys/class/bdi//min_bytes knob Documentation/ABI/testing/sysfs-class-bdi | 40 +++++++ include/linux/backing-dev.h | 8 ++ mm/backing-dev.c | 93 +++++++++++++++- mm/page-writeback.c | 127 ++++++++++++++++++++-- 4 files changed, 254 insertions(+), 14 deletions(-) base-commit: 247f34f7b80357943234f93f247a1ae6b6c3a740