On 3/2/26 04:45, Andre Ramos wrote: > Introduce /dev/ampress, a bidirectional fd-based interface for > cooperative memory reclaim between the kernel and userspace.
I'm very sure this should be tagged as RFC. > > Userspace processes open /dev/ampress and block on read() to receive > struct ampress_event notifications carrying a graduated urgency level > (LOW/MEDIUM/HIGH/FATAL), the NUMA node of the pressure source, and a > suggested reclaim target in KiB. After freeing memory the process > issues AMPRESS_IOC_ACK to close the feedback loop. > > The feature hooks into balance_pgdat() in mm/vmscan.c, mapping the > kswapd scan priority to urgency bands: > priority 10-12 -> LOW > priority 7-9 -> MEDIUM > priority 4-6 -> HIGH > priority 1-3 -> FATAL > > ampress_notify() is IRQ-safe (read_lock_irqsave + spin_lock_irqsave, > no allocations) so it can be called from any reclaim context. > Per-subscriber events overwrite without queuing to prevent unbounded > backlog. A debugfs trigger at /sys/kernel/debug/ampress/inject allows > testing without real memory pressure. [...] > > +ADAPTIVE MEMORY PRESSURE SIGNALING (AMPRESS) > +M: Darabat <[email protected]> > +L: [email protected] > +S: Maintained > +F: include/linux/ampress.h > +F: include/trace/events/ampress.h > +F: include/uapi/linux/ampress.h > +F: mm/ampress.c > +F: mm/ampress_test.c > +F: tools/testing/ampress/ We generally don't make new kernel contributors MM maintainers. But what sticks out more is the inconsistency between your name+mail and "Darabat <[email protected]>". -- Cheers, David
