I would like to revisit Qu's proposal to not charge btrfs extent_buffer allocations to the user's cgroup. https://lore.kernel.org/linux-mm/b5fef5372ae454a7b6da4f2f75c427aeab6a07d6.1727498749.git.wqu@xxxxxxxx/ I believe it is detrimental to randomly account these global pages to the cgroup using them, basically at random. A bit more justification and explanation in the patches themselves. --- Changelog: v3: - use mod_node_page_state since we will never count cgroup stats - include Shakeel's patch that removes a WARNING triggered by this series v2: - switch from filemap_add_folio_nocharge() to AS_UNCHARGED on the address_space. - fix an interrupt safety bug in the vmstat patch. - fix some foolish build errors for CONFIG_MEMCG=n Boris Burkov (3): mm/filemap: add AS_UNCHARGED mm: add vmstat for cgroup uncharged pages btrfs: set AS_UNCHARGED on the btree_inode Shakeel Butt (1): memcg: remove warning from folio_lruvec fs/btrfs/disk-io.c | 1 + include/linux/memcontrol.h | 5 +---- include/linux/mmzone.h | 3 +++ include/linux/pagemap.h | 1 + mm/filemap.c | 29 +++++++++++++++++++++++++---- mm/vmstat.c | 3 +++ 6 files changed, 34 insertions(+), 8 deletions(-) -- 2.50.1
