Hi Matthew, On Sat, Jul 4, 2020 at 3:01 PM Matthew Wilcox <willy@xxxxxxxxxxxxx> wrote: > One of the things we (mostly Mike Kravetz) found recently when debugging > a memory allocation stall issue is that this message does not capture > the state which actually caused the message to be printed. In the > intervening time between the memory allocation failure being detected > and this message being printed, kswapd may have made forward progress. Oh, right, makes sense. Worth fixing, of course, but probably not so easy to do. - Pekka
