On Thu, Jan 26, 2023 at 08:41:34AM +0100, Michal Hocko wrote: > On Wed 25-01-23 15:14:48, Roman Gushchin wrote: > > On Wed, Jan 25, 2023 at 03:22:00PM -0300, Marcelo Tosatti wrote: > > > On Wed, Jan 25, 2023 at 08:06:46AM -0300, Leonardo Brás wrote: > > > > On Wed, 2023-01-25 at 09:33 +0100, Michal Hocko wrote: > > > > > On Wed 25-01-23 04:34:57, Leonardo Bras wrote: > > > > > > Disclaimer: > > > > > > a - The cover letter got bigger than expected, so I had to split it in > > > > > > sections to better organize myself. I am not very confortable with it. > > > > > > b - Performance numbers below did not include patch 5/5 (Remove flags > > > > > > from memcg_stock_pcp), which could further improve performance for > > > > > > drain_all_stock(), but I could only notice the optimization at the > > > > > > last minute. > > > > > > > > > > > > > > > > > > 0 - Motivation: > > > > > > On current codebase, when drain_all_stock() is ran, it will schedule a > > > > > > drain_local_stock() for each cpu that has a percpu stock associated with a > > > > > > descendant of a given root_memcg. > > > > Do you know what caused those drain_all_stock() calls? I wonder if we should look > > into why we have many of them and whether we really need them? > > > > It's either some user's actions (e.g. reducing memory.max), either some memcg > > is entering pre-oom conditions. In the latter case a lot of drain calls can be > > scheduled without a good reason (assuming the cgroup contain multiple tasks running > > on multiple cpus). > > I believe I've never got a specific answer to that. We > have discussed that in the previous version submission > (20221102020243.522358-1-leobras@xxxxxxxxxx and specifically > Y2TQLavnLVd4qHMT@xxxxxxxxxxxxxx). Leonardo has mentioned a mix of RT and > isolcpus. I was wondering about using memcgs in RT workloads because > that just sounds weird but let's say this is the case indeed. This could be the case. You can consider an "edge device" where it is necessary to run a RT workload. It might also be useful to run non realtime applications on the same system. > Then an RT task or whatever task that is running on an isolated > cpu can have pcp charges. Usually the RT task (or more specifically the realtime sensitive loop of the application) runs entirely on userspace. But i suppose there could be charges on application startup. > > Essentially each cpu will try to grab the remains of the memory quota > > and move it locally. I wonder in such circumstances if we need to disable the pcp-caching > > on per-cgroup basis. > > I think it would be more than sufficient to disable pcp charging on an > isolated cpu. This is not a per memcg property. I can imagine that > different tasks running in the same memcg can run on a mix of CPUs (e.g. > only part of it on isolated CPUs). It is a recipe for all sorts of > priority inversions but well, memcg and RT is there already. I suppose the more general the solution, the better. > > Generally speaking, draining of pcpu stocks is useful only if an idle cpu is holding some > > charges/memcg references (it might be not completely idle, but running some very special > > workload which is not doing any kernel allocations or a process belonging to the root memcg). > > In all other cases pcpu stock will be either drained naturally by an allocation from another > > memcg or an allocation from the same memcg will "restore" it, making draining useless. > > > > We also can into drain_all_pages() opportunistically, without waiting for the result. > > On a busy system it's most likely useless, we might oom before scheduled works will be executed. > > I think the primary objective is that no userspace unintended execution > happens on isolated cpus. No interruptions to the userspace code (time sensitive code) running on isolated CPUs: no IPIs, no task switches. > > I admit I planned to do some work around and even started, but then never had enough time to > > finish it. > > > > Overall I'm somewhat resistant to an idea of making generic allocation & free paths slower > > for an improvement of stock draining. It's not a strong objection, but IMO we should avoid > > doing this without a really strong reason. > > Are you OK with a simple opt out on isolated CPUs? That would make > charges slightly slower (atomic on the hierarchy counters vs. a single > pcp adjustment) but it would guarantee that the isolated workload is > predictable which is the primary objective AFAICS. This would make isolated CPUs "second class citizens": it would be nice to be able to execute non realtime apps on isolated CPUs as well (think of different periods of time during a day, one where more realtime apps are required, another where less realtime apps are required). Concrete example: think of a computer handling vRAN traffic near a cell tower. The traffic (therefore amount of processing required by realtime applications) might vary during the day. User might want to run containers that depend on good memcg charging performance on isolated CPUs.
