On Tue, 2017-05-23 at 10:23 -0400, Josef Bacik wrote: > My approach here is twofold. First, keep track of the difference in > inactive and slab pages since the last time kswapd ran. In the first > run this will just be the overall counts of inactive and slab, but > for > each subsequent run we'll have a good idea of where the memory > pressure > is coming from. Then we use this information to put pressure on > either > the inactive lists or the slab caches, depending on where the > pressure > is coming from. > Signed-off-by: Josef Bacik <jbacik@xxxxxx> This looks totally reasonable to me. Acked-by: Rik van Riel <riel@xxxxxxxxxx>
Attachment:
signature.asc
Description: This is a digitally signed message part
