On Tue, Apr 20, 2021 at 06:18:29PM -0700, Shakeel Butt wrote: > On Tue, Apr 20, 2021 at 12:18 PM Roman Gushchin <guro@xxxxxx> wrote: > > > > On Mon, Apr 19, 2021 at 06:44:02PM -0700, Shakeel Butt wrote: > [...] > > > 1. prctl(PF_MEMALLOC) > > > > > > The idea is to give userspace oom-killer (just one thread which is > > > finding the appropriate victims and will be sending SIGKILLs) access > > > to MEMALLOC reserves. Most of the time the preallocation, mlock and > > > memory.min will be good enough but for rare occasions, when the > > > userspace oom-killer needs to allocate, the PF_MEMALLOC flag will > > > protect it from reclaim and let the allocation dip into the memory > > > reserves. > > > > > > The misuse of this feature would be risky but it can be limited to > > > privileged applications. Userspace oom-killer is the only appropriate > > > user of this feature. This option is simple to implement. > > > > Hello Shakeel! > > > > If ordinary PAGE_SIZE and smaller kernel allocations start to fail, > > the system is already in a relatively bad shape. Arguably the userspace > > OOM killer should kick in earlier, it's already a bit too late. > > Please note that these are not allocation failures but rather reclaim > on allocations (which is very normal). Our observation is that this > reclaim is very unpredictable and depends on the type of memory > present on the system which depends on the workload. If there is a > good amount of easily reclaimable memory (e.g. clean file pages), the > reclaim would be really fast. However for other types of reclaimable > memory the reclaim time varies a lot. The unreclaimable memory, pinned > memory, too many direct reclaimers, too many isolated memory and many > other things/heuristics/assumptions make the reclaim further > non-deterministic. > > In our observation the global reclaim is very non-deterministic at the > tail and dramatically impacts the reliability of the system. We are > looking for a solution which is independent of the global reclaim. > > > Allowing to use reserves just pushes this even further, so we're risking > > the kernel stability for no good reason. > > Michal has suggested ALLOC_OOM which is less risky. The problem is that even if you'll serve the oom daemon task with pages from a reserve/custom pool, it doesn't guarantee anything, because the task still can wait for a long time on some mutex, taken by another process, throttled somewhere in the reclaim. You're basically trying to introduce a "higher memory priority" and as always in such cases there will be priority inversion problems. So I doubt that you can simple create a common mechanism which will work flawlessly for all kinds of allocations, I anticipate many special cases requiring an individual approach. > > > > > But I agree that throttling the oom daemon in direct reclaim makes no sense. > > I wonder if we can introduce a per-task flag which will exclude the task from > > throttling, but instead all (large) allocations will just fail under a > > significant memory pressure more easily. In this case if there is a significant > > memory shortage the oom daemon will not be fully functional (will get -ENOMEM > > for an attempt to read some stats, for example), but still will be able to kill > > some processes and make the forward progress. > > So, the suggestion is to have a per-task flag to (1) indicate to not > throttle and (2) fail allocations easily on significant memory > pressure. > > For (1), the challenge I see is that there are a lot of places in the > reclaim code paths where a task can get throttled. There are > filesystems that block/throttle in slab shrinking. Any process can get > blocked on an unrelated page or inode writeback within reclaim. > > For (2), I am not sure how to deterministically define "significant > memory pressure". One idea is to follow the __GFP_NORETRY semantics > and along with (1) the userspace oom-killer will see ENOMEM more > reliably than stucking in the reclaim. > > So, the oom-killer maintains a list of processes to kill in extreme > conditions, have their pidfds open and keep that list fresh. Whenever > any syscalls returns ENOMEM, it starts doing > pidfd_send_signal(SIGKILL) to that list of processes, right? > > The idea has merit but I don't see how this is any simpler. The (1) is > challenging on its own and my main concern is that it will be very > hard to maintain as reclaim code (particularly shrinkers) callbacks > into many diverse subsystems. Yeah, I thought about something like this, but I didn't go too deep. Basically we can emulate __GFP_NOFS | __GFP_NORETRY, but I'm not sure we can apply it for any random allocation without bad consequences. Btw, this approach can be easily prototyped using bpf: a bpf program can be called on each allocation and modify the behavior based on the pid of the process and other circumstances. > > > But maybe it can be done in userspace too: by splitting the daemon into > > a core- and extended part and avoid doing anything behind bare minimum > > in the core part. > > > > > > > > 2. Mempool > > > > > > The idea is to preallocate mempool with a given amount of memory for > > > userspace oom-killer. Preferably this will be per-thread and > > > oom-killer can preallocate mempool for its specific threads. The core > > > page allocator can check before going to the reclaim path if the task > > > has private access to the mempool and return page from it if yes. > > > > > > This option would be more complicated than the previous option as the > > > lifecycle of the page from the mempool would be more sophisticated. > > > Additionally the current mempool does not handle higher order pages > > > and we might need to extend it to allow such allocations. Though this > > > feature might have more use-cases and it would be less risky than the > > > previous option. > > > > It looks like an over-kill for the oom daemon protection, but if there > > are other good use cases, maybe it's a good feature to have. > > > > IMHO it is not an over-kill and easier to do then to remove all > instances of potential blocking/throttling sites in memory reclaim. > > > > > > > Another idea I had was to use kthread based oom-killer and provide the > > > policies through eBPF program. Though I am not sure how to make it > > > monitor arbitrary metrics and if that can be done without any > > > allocations. > > > > To start this effort it would be nice to understand what metrics various > > oom daemons use and how easy is to gather them from the bpf side. I like > > this idea long-term, but not sure if it has been settled down enough. > > I imagine it will require a fair amount of work on the bpf side, so we > > need a good understanding of features we need. > > > > Are there any examples of gathering existing metrics from bpf? Suren > has given a list of metrics useful for Android. Is it possible to > gather those metrics? First, I need to admit that I didn't follow the bpf development too close for last couple of years, so my knowledge can be a bit outdated. But in general bpf is great when there is a fixed amount of data as input (e.g. skb) and a fixed output (e.g. drop/pass the packet). There are different maps which are handy to store some persistent data between calls. However traversing complex data structures is way more complicated. It's especially tricky if the data structure is not of a fixed size: bpf programs have to be deterministic, so there are significant constraints on loops. Just for example: it's easy to call a bpf program for each task in the system, provide some stats/access to some fields of struct task and expect it to return an oom score, which then the kernel will look at to select the victim. Something like this can be done with cgroups too. Writing a kthread, which can sleep, poll some data all over the system and decide what to do (what oomd/... does), will be really challenging. And going back, it will not provide any guarantees unless we're not taking any locks, which is already quite challenging. Thanks!
