From: Michal Hocko <mhocko@suse.com> To: Tejun Heo <tj@kernel.org> Cc: "Wei Xu" <weixugc@google.com>, "Yosry Ahmed" <yosryahmed@google.com>, "Andrew Morton" <akpm@linux-foundation.org>, "Johannes Weiner" <hannes@cmpxchg.org>, "Roman Gushchin" <roman.gushchin@linux.dev>, "Shakeel Butt" <shakeelb@google.com>, "Muchun Song" <muchun.song@linux.dev>, "Ivan Babrou" <ivan@cloudflare.com>, "Michal Koutný" <mkoutny@suse.com>, "Waiman Long" <longman@redhat.com>, linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, "Greg Thelen" <gthelen@google.com> Subject: Re: [PATCH v4 4/4] mm: memcg: use non-unified stats flushing for userspace reads Date: Tue, 12 Sep 2023 13:03:00 +0200 [thread overview] Message-ID: <ZQBFZMRL8WmqRgrM@dhcp22.suse.cz> (raw) In-Reply-To: <ZP92xP5rdKdeps7Z@mtj.duckdns.org> On Mon 11-09-23 10:21:24, Tejun Heo wrote: > Hello, > > On Mon, Sep 11, 2023 at 01:01:25PM -0700, Wei Xu wrote: > > Yes, it is the same test (10K contending readers). The kernel change > > is to remove stats_user_flush_mutex from mem_cgroup_user_flush_stats() > > so that the concurrent mem_cgroup_user_flush_stats() requests directly > > contend on cgroup_rstat_lock in cgroup_rstat_flush(). > > I don't think it'd be a good idea to twist rstat and other kernel internal > code to accommodate 10k parallel readers. I didn't mean to suggest optimizing for this specific scenario. I was mostly curious whether the pathological case of unbound high latency due to lock dropping is easy to trigger by huge number of readers. It seems it is not and the mutex might not be really needed as a prevention. > If we want to support that, let's > explicitly support that by implementing better batching in the read path. Well, we need to be able to handle those situations because stat files are generally readable and we do not want unrelated workloads to influence each other heavily through this path. [...] > When you have that many concurrent readers, most of them won't need to > actually flush. Agreed! -- Michal Hocko SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko-IBi9RG/b67k@public.gmane.org> To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Cc: "Wei Xu" <weixugc-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>, "Yosry Ahmed" <yosryahmed-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>, "Andrew Morton" <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>, "Johannes Weiner" <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>, "Roman Gushchin" <roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org>, "Shakeel Butt" <shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>, "Muchun Song" <muchun.song-fxUVXftIFDnyG1zEObXtfA@public.gmane.org>, "Ivan Babrou" <ivan-lDpJ742SOEtZroRs9YW3xA@public.gmane.org>, "Michal Koutný" <mkoutny-IBi9RG/b67k@public.gmane.org>, "Waiman Long" <longman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Greg Thelen" <gthelen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org> Subject: Re: [PATCH v4 4/4] mm: memcg: use non-unified stats flushing for userspace reads Date: Tue, 12 Sep 2023 13:03:00 +0200 [thread overview] Message-ID: <ZQBFZMRL8WmqRgrM@dhcp22.suse.cz> (raw) In-Reply-To: <ZP92xP5rdKdeps7Z-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org> On Mon 11-09-23 10:21:24, Tejun Heo wrote: > Hello, > > On Mon, Sep 11, 2023 at 01:01:25PM -0700, Wei Xu wrote: > > Yes, it is the same test (10K contending readers). The kernel change > > is to remove stats_user_flush_mutex from mem_cgroup_user_flush_stats() > > so that the concurrent mem_cgroup_user_flush_stats() requests directly > > contend on cgroup_rstat_lock in cgroup_rstat_flush(). > > I don't think it'd be a good idea to twist rstat and other kernel internal > code to accommodate 10k parallel readers. I didn't mean to suggest optimizing for this specific scenario. I was mostly curious whether the pathological case of unbound high latency due to lock dropping is easy to trigger by huge number of readers. It seems it is not and the mutex might not be really needed as a prevention. > If we want to support that, let's > explicitly support that by implementing better batching in the read path. Well, we need to be able to handle those situations because stat files are generally readable and we do not want unrelated workloads to influence each other heavily through this path. [...] > When you have that many concurrent readers, most of them won't need to > actually flush. Agreed! -- Michal Hocko SUSE Labs
next prev parent reply other threads:[~2023-09-12 11:03 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-31 16:56 [PATCH v4 0/4] memcg: non-unified flushing for userspace stats Yosry Ahmed 2023-08-31 16:56 ` Yosry Ahmed 2023-08-31 16:56 ` [PATCH v4 1/4] mm: memcg: properly name and document unified stats flushing Yosry Ahmed 2023-09-04 14:44 ` Michal Hocko 2023-09-04 14:44 ` Michal Hocko 2023-09-05 15:55 ` Yosry Ahmed 2023-09-05 15:55 ` Yosry Ahmed 2023-08-31 16:56 ` [PATCH v4 2/4] mm: memcg: add a helper for non-unified " Yosry Ahmed 2023-08-31 16:56 ` Yosry Ahmed 2023-09-04 14:45 ` Michal Hocko 2023-09-04 14:45 ` Michal Hocko 2023-08-31 16:56 ` [PATCH v4 3/4] mm: memcg: let non-unified root stats flushes help unified flushes Yosry Ahmed 2023-08-31 16:56 ` Yosry Ahmed 2023-09-04 14:50 ` Michal Hocko 2023-09-04 15:29 ` Michal Koutný 2023-09-04 15:29 ` Michal Koutný 2023-09-04 15:41 ` Michal Hocko 2023-09-04 15:41 ` Michal Hocko 2023-09-05 14:10 ` Michal Koutný 2023-09-05 14:10 ` Michal Koutný 2023-09-05 15:54 ` Yosry Ahmed 2023-09-05 15:54 ` Yosry Ahmed 2023-09-05 16:07 ` Michal Koutný 2023-09-05 16:07 ` Michal Koutný 2023-09-12 11:03 ` Michal Hocko 2023-09-12 11:03 ` Michal Hocko 2023-08-31 16:56 ` [PATCH v4 4/4] mm: memcg: use non-unified stats flushing for userspace reads Yosry Ahmed 2023-08-31 16:56 ` Yosry Ahmed 2023-09-04 15:15 ` Michal Hocko 2023-09-04 15:15 ` Michal Hocko 2023-09-05 15:57 ` Yosry Ahmed 2023-09-05 15:57 ` Yosry Ahmed 2023-09-08 0:52 ` Wei Xu 2023-09-08 0:52 ` Wei Xu 2023-09-08 1:02 ` Ivan Babrou 2023-09-08 1:02 ` Ivan Babrou 2023-09-08 1:11 ` Yosry Ahmed 2023-09-08 1:11 ` Yosry Ahmed 2023-09-11 13:11 ` Michal Hocko 2023-09-11 19:15 ` Wei Xu 2023-09-11 19:15 ` Wei Xu 2023-09-11 19:34 ` Michal Hocko 2023-09-11 19:34 ` Michal Hocko 2023-09-11 20:01 ` Wei Xu 2023-09-11 20:21 ` Tejun Heo 2023-09-11 20:28 ` Yosry Ahmed 2023-09-11 20:28 ` Yosry Ahmed 2023-09-12 11:03 ` Michal Hocko [this message] 2023-09-12 11:03 ` Michal Hocko 2023-09-12 11:09 ` Yosry Ahmed 2023-09-12 11:09 ` Yosry Ahmed 2023-08-31 17:18 ` [PATCH v4 0/4] memcg: non-unified flushing for userspace stats Waiman Long 2023-08-31 17:18 ` Waiman Long
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=ZQBFZMRL8WmqRgrM@dhcp22.suse.cz \ --to=mhocko@suse.com \ --cc=akpm@linux-foundation.org \ --cc=cgroups@vger.kernel.org \ --cc=gthelen@google.com \ --cc=hannes@cmpxchg.org \ --cc=ivan@cloudflare.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=longman@redhat.com \ --cc=mkoutny@suse.com \ --cc=muchun.song@linux.dev \ --cc=roman.gushchin@linux.dev \ --cc=shakeelb@google.com \ --cc=tj@kernel.org \ --cc=weixugc@google.com \ --cc=yosryahmed@google.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.