From: Wu Fengguang <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
David Rientjes <rientjes@google.com>,
Hugh Dickins <hugh@veritas.com>, Ingo Molnar <mingo@elte.hu>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
Mike Waychison <mikew@google.com>, Nick Piggin <npiggin@suse.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rohit Seth <rohitseth@google.com>, Edwin <edwintorok@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ying Han <yinghan@google.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 00/14] filemap and readahead fixes
Date: Fri, 10 Apr 2009 13:53:17 +0800 [thread overview]
Message-ID: <20090410055317.GA11854@localhost> (raw)
In-Reply-To: <20090409220815.22ef8b21.akpm@linux-foundation.org>
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@intel.com> 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@intel.com> 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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-04-10 5:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 11:50 [PATCH 00/14] filemap and readahead fixes Wu Fengguang
2009-04-07 11:50 ` [PATCH 01/14] mm: fix find_lock_page_retry() return value parsing Wu Fengguang
2009-04-07 11:50 ` [PATCH 02/14] mm: fix major/minor fault accounting on retried fault Wu Fengguang
2009-04-07 11:50 ` [PATCH 03/14] mm: remove FAULT_FLAG_RETRY dead code Wu Fengguang
2009-04-07 11:50 ` [PATCH 04/14] mm: reduce duplicate page fault code Wu Fengguang
2009-04-07 11:50 ` [PATCH 05/14] readahead: account mmap_miss for VM_FAULT_RETRY Wu Fengguang
2009-04-07 11:50 ` [PATCH 06/14] readahead: move max_sane_readahead() calls into force_page_cache_readahead() Wu Fengguang
2009-04-07 11:50 ` [PATCH 07/14] readahead: apply max_sane_readahead() limit in ondemand_readahead() Wu Fengguang
2009-04-07 11:50 ` [PATCH 08/14] readahead: remove one unnecessary radix tree lookup Wu Fengguang
2009-04-07 11:50 ` [PATCH 09/14] readahead: increase interleaved readahead size Wu Fengguang
2009-04-07 11:50 ` [PATCH 10/14] readahead: remove sync/async readahead call dependency Wu Fengguang
2009-04-07 11:50 ` [PATCH 11/14] readahead: clean up and simplify the code for filemap page fault readahead Wu Fengguang
2009-04-07 15:50 ` Linus Torvalds
2009-04-07 11:50 ` [PATCH 12/14] readahead: sequential mmap readahead Wu Fengguang
2009-04-07 11:50 ` [PATCH 13/14] readahead: enforce full readahead size on async " Wu Fengguang
2009-04-07 11:50 ` [PATCH 14/14] readahead: record mmap read-around states in file_ra_state Wu Fengguang
2009-04-10 4:36 ` [PATCH 00/14] filemap and readahead fixes Andrew Morton
2009-04-10 4:54 ` Wu Fengguang
2009-04-10 5:08 ` Andrew Morton
2009-04-10 5:53 ` Wu Fengguang [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-07 7:17 Wu Fengguang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090410055317.GA11854@localhost \
--to=fengguang.wu@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=edwintorok@gmail.com \
--cc=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikew@google.com \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=rientjes@google.com \
--cc=rohitseth@google.com \
--cc=yinghan@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).