[lkml]   [2018]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 4/4] mm: use the cached page for filemap_fault
On Wed 05-12-18 09:58:10, Josef Bacik wrote:
> On Tue, Dec 04, 2018 at 02:50:34PM -0800, Andrew Morton wrote:
> > On Fri, 30 Nov 2018 14:58:12 -0500 Josef Bacik <> wrote:
> >
> > > If we drop the mmap_sem we have to redo the vma lookup which requires
> > > redoing the fault handler. Chances are we will just come back to the
> > > same page, so save this page in our vmf->cached_page and reuse it in the
> > > next loop through the fault handler.
> > >
> >
> > Is this really worthwhile? Rerunning the fault handler is rare (we
> > hope) and a single pagecache lookup is fast.
> >
> > Some performance testing results would be helpful here. It's
> > practically obligatory when claiming a performance improvement.
> >
> >
> Honestly the big thing is just not doing IO under the mmap_sem. I had this
> infrastructure originally for the mkwrite portion of these patches that I
> dropped, because I was worried about the page being messed with after we did all
> the mkwrite work. However since I'm not doing that anymore there's less of a
> need for it. I have no performance numbers for this, just seemed like a good
> idea since we are likely to just have the page again, and this keeps us from
> evicting the page right away and causing more thrashing.
> I'll try and set something up to see if there's a difference. If there's no
> difference do you want me to drop this? Thanks,

If there's no difference, I'd like to drop this as well. It just
complicates the fault state handling which is already complex enough.

Jan Kara <>

 \ /
  Last update: 2018-12-07 12:04    [W:0.051 / U:29.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site