Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp2985453ybt; Mon, 29 Jun 2020 12:09:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw7CGeX5PyXN4ibXaOR+qfnvC7cc3bvzmSACRUMsCX2bf9CnOrbdaHzRqLTmVOIVQnLLwjo X-Received: by 2002:a17:906:7c54:: with SMTP id g20mr15643051ejp.460.1593457743595; Mon, 29 Jun 2020 12:09:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593457743; cv=none; d=google.com; s=arc-20160816; b=hGI3aVvqXEWXFS9Rc/zLm7HrGycNvijf+o4jD33z997CJaWQblppwpSg4ABLLlY3Bt B9vZbUe9TKKodrtPSyK9B85uJo3TBplHsPu/+f8IxAcZGc7jgyjGFt4YicwBcMAiZEaS 0Yunbk+t17RwUwx8jA1WEzZhYLQTWzCqF7JbgpaYfzN/Ijh0RhwJkFgreJ79zLAiPOHd elvEE6PxxeMikxRKpv6rjUVMsYMM4lPEZsx4wDr4K5cip6FPrKWl/ZFd8uWlqRYz/lNW OE2gmesXYJ0WFylWZGUOAGPKQXRYu3qTjG0pXMHq1S4hn4XxhfOLXeoKVeTp78K87n7c 5IbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:mime-version:user-agent:date:message-id:subject:cc :to:from:dkim-signature; bh=n2qVe7QVtMWlsu3tW293XYJBZ3r5SYGfqQyhGd9NB2s=; b=jwGmOzhMU75PHlqL08vYp+OSBdrIPh0Hm+/umwMrIUj4Zy2MbiX2+K0fl88OuLu+kM buRVjz/IP7Pr5WrCPPeB0x+TqzS8yH9NucY8pxjh08N6Lt4DqIxjBC4rQqWUnAxvZvs9 dyPBOAiWdc8KwvfzQlNH4K/sbM2y32Tv9GoQfU75mBX2fqxn2gI1Rghtu+vkE+PD0c6P liry0GD6y2RFOKne8SlVTTVT+C+7NcP4NTHmrW/MIcypeawbeWgZmdybYMZqoKjf4sBm TDnD5/yVaMXxGTEeC9S6lk25XPxDwifHhf5bNoLJhp3GBQ7QML0icghSDEJLNktMHfd0 Ri6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Ij4PBgcS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id pw26si324952ejb.240.2020.06.29.12.08.39; Mon, 29 Jun 2020 12:09:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Ij4PBgcS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729845AbgF2TIc (ORCPT + 99 others); Mon, 29 Jun 2020 15:08:32 -0400 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:55906 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730889AbgF2TI0 (ORCPT ); Mon, 29 Jun 2020 15:08:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1593457705; 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; bh=n2qVe7QVtMWlsu3tW293XYJBZ3r5SYGfqQyhGd9NB2s=; b=Ij4PBgcSg3Ntims8eYjhczQG0ARN8QglfAWrodFofst2aw7QaYiOcET3Hw72LrnenPGKes 0ZCiaX6ecA50df/o7VpoyZjad6QJlmHXU+17fcI0hsUFPZwB5BlSZ2ZdhtPaMs9X8O2wfb +3QqEPmzBVN82VzSlgZ8g/Pwe4cSavg= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-240-L3fpmOSlM7CetVm3iyl5YQ-1; Mon, 29 Jun 2020 15:08:13 -0400 X-MC-Unique: L3fpmOSlM7CetVm3iyl5YQ-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B3B1210059A3; Mon, 29 Jun 2020 19:08:11 +0000 (UTC) Received: from [IPv6:::1] (ovpn04.gateway.prod.ext.phx2.redhat.com [10.5.9.4]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 074F960BF3; Mon, 29 Jun 2020 19:08:10 +0000 (UTC) From: Eric Sandeen To: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Jonathan Corbet Cc: cgroups@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-xfs Subject: [PATCH] doc: cgroup: add f2fs and xfs to supported list for writeback Message-ID: Date: Mon, 29 Jun 2020 14:08:09 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org f2fs and xfs have both added support for cgroup writeback: 578c647 f2fs: implement cgroup writeback support adfb5fb xfs: implement cgroup aware writeback so add them to the supported list in the docs. Signed-off-by: Eric Sandeen --- TBH I wonder about the wisdom of having this detail in the doc, as it apparently gets missed quite often ... diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst index ce3e05e..4f82afa 100644 --- a/Documentation/admin-guide/cgroup-v2.rst +++ b/Documentation/admin-guide/cgroup-v2.rst @@ -1684,9 +1684,9 @@ per-cgroup dirty memory states are examined and the more restrictive of the two is enforced. cgroup writeback requires explicit support from the underlying -filesystem. Currently, cgroup writeback is implemented on ext2, ext4 -and btrfs. On other filesystems, all writeback IOs are attributed to -the root cgroup. +filesystem. Currently, cgroup writeback is implemented on ext2, ext4, +btrfs, f2fs, and xfs. On other filesystems, all writeback IOs are +attributed to the root cgroup. There are inherent differences in memory and writeback management which affects how cgroup ownership is tracked. Memory is tracked per