Re: [PATCH 0/7] mm: Improve swap path scalability with batched operations
From: Tim Chen
Date: Thu May 05 2016 - 11:57:44 EST
On Thu, 2016-05-05 at 09:49 +0200, Michal Hocko wrote:
> On Wed 04-05-16 17:25:06, Johannes Weiner wrote:
> >
> >Â
>
> >
> > >
> > > >
> > > > I understand that the patch set is a little large. Any better
> > > > ideas for achieving similar ends will be appreciated. ÂI put
> > > > out these patches in the hope that it will spur solutions
> > > > to improve swap.
> > > >
> > > > Perhaps the first two patches to make shrink_page_list into
> > > > smaller components can be considered first, as a first stepÂ
> > > > to make any changes to the reclaim code easier.
> > It makes sense that we need to batch swap allocation and swap cache
> > operations. Unfortunately, the patches as they stand turn
> > shrink_page_list() into an unreadable mess. This would need better
> > refactoring before considering them for upstream merging. The swap
> > allocation batching should not obfuscate the main sequence of
> > events
> > that is happening for both file-backed and anonymous pages.
> That was my first impression as well but to be fair I only skimmed
> through the patch so I might be just biased by the size.
>
> >
> > It'd also be great if the remove_mapping() batching could be done
> > universally for all pages, given that in many cases file pages from
> > the same inode also cluster together on the LRU.
>
Agree. ÂI didn't try to do something on file mapped pages yet as
the changes in this patch set is already quite substantial.
But once we have some agreement on the batching on the anonymous
pages, the file backed pages could be grouped similarly.
Tim