Re: [PATCH 00/14] filemap and readahead fixes

[Wu Fengguang]

On Fri, Apr 10, 2009 at 01:08:15PM +0800, Andrew Morton wrote:
> On Fri, 10 Apr 2009 12:54:40 +0800 Wu Fengguang <fengguang.wu@xxxxxxxxx> wrote:
> 
> > On Fri, Apr 10, 2009 at 12:36:43PM +0800, Andrew Morton wrote:
> > > On Tue, 07 Apr 2009 19:50:39 +0800 Wu Fengguang <fengguang.wu@xxxxxxxxx> wrote:
> > > 
> > > > This is a set of fixes and cleanups for filemap and readahead.
> > > 
> > > Unfortunately page_fault-retry-with-nopage_retry.patch got dropped so
> > > the first five patches are no longer applicable.  Patch #11 also died.
> > > 
> > > Can you please respin the remains against current mainline?
> > 
> > Do you mean rebase them onto linux-next, bypassing Ying Hans' patches?
> > 
> 
> Those patches are still several akpm-hours ahead in my backlog queue. 
> They don't seem to have generated much attention and someone (ie: you)
> had substantial comments which haven't been replied to yet.  So I'd
> expect another version to be forthcoming.

OK. The truth on my part is that I'll be able to submit my patches
much earlier if her patches are not in the way. I have to understand
what her patches do and resolve conflicts and retest and resolve the
side effects.

So I became a big tester of her patches and cleared several bugs out
of it. Now I feel confident on the fault-retry patches.

I can imagine one major benefited workload to be concurrent threads
reading on the same mmap file. Before her patch:
- minor faults are blocked waiting for major faults doing IO
- major faults block each other, leading to _serialized_ IO
So her patches not only reduce unnecessary long waited locks,
but also make _parallel_ IOs happen.

> But I don't mind either way.  I guess the main question here is: do we
> see a need to squeeze any of these things into 2.6.30?

Linus and mine filemap/readahead patches are in fact pretty old bug
fixing and cleanup ones, they should be safe for 2.6.30 :-)

Thanks,
Fengguang

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/