From: Fengguang Wu <wfg@mail.ustc.edu.cn>
To: Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] radixtree: introduce radix_tree_scan_hole()
Date: Mon, 23 Jul 2007 16:12:09 +0800 [thread overview]
Message-ID: <385179010.25899@ustc.edu.cn> (raw)
Message-ID: <20070723081209.GA12393@mail.ustc.edu.cn> (raw)
In-Reply-To: <20070723080405.GA7420@mail.ustc.edu.cn>
On Mon, Jul 23, 2007 at 04:04:05PM +0800, Fengguang Wu wrote:
> On Mon, Jul 23, 2007 at 05:58:02PM +1000, Nick Piggin wrote:
> > Fengguang Wu wrote:
> > >Introduce radix_tree_scan_hole(root, index, max_scan) to scan radix tree
> > >for the first hole. It will be used in interleaved readahead.
> > >
> > >The implementation is dumb and obviously correct.
> > >It can help debug(and document) the possible smart one in future.
> >
> > Reasonable function to want. Is radix_tree_scan_hole the best name?
> > What about radix_tree_next_hole or _find_next_hole? (Andrew, any
> > suggestions?)
>
> Thank you!
>
> All comments seems reasonable, so I simply attach the updated patch.
>
> Fengguang
> ---
> Subject: radixtree: introduce radix_tree_next_hole()
> Cc: Nick Piggin <nickpiggin@yahoo.com.au>
>
> Introduce radix_tree_next_hole(root, index, max_scan) to scan radix tree
> for the first hole. It will be used in interleaved readahead.
>
> Cc: Nick Piggin <nickpiggin@yahoo.com.au>
> Signed-off-by: Fengguang Wu <wfg@mail.ustc.edu.cn>
And another rename fix for the interleaved readahead patch.
Signed-off-by: Fengguang Wu <wfg@mail.ustc.edu.cn>
---
mm/readahead.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.22-rc6-mm1.orig/mm/readahead.c
+++ linux-2.6.22-rc6-mm1/mm/readahead.c
@@ -372,7 +372,7 @@ ondemand_readahead(struct address_space
pgoff_t start;
read_lock_irq(&mapping->tree_lock);
- start = radix_tree_scan_hole(&mapping->page_tree, offset, max+1);
+ start = radix_tree_next_hole(&mapping->page_tree, offset, max+1);
read_unlock_irq(&mapping->tree_lock);
if (!start || start - offset > max)
next prev parent reply other threads:[~2007-07-23 8:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 4:43 [PATCH 0/7] readahead cleanups and interleaved readahead take 3 Fengguang Wu
2007-07-21 4:43 ` Fengguang Wu
2007-07-21 4:43 ` [PATCH 1/7] readahead: compacting file_ra_state Fengguang Wu
2007-07-21 4:43 ` Fengguang Wu
2007-07-21 4:43 ` [PATCH 2/7] readahead: mmap read-around simplification Fengguang Wu
2007-07-21 4:43 ` Fengguang Wu
2007-07-21 4:43 ` [PATCH 3/7] readahead: combine file_ra_state.prev_index/prev_offset into prev_pos Fengguang Wu
2007-07-21 4:43 ` Fengguang Wu
2007-07-21 4:43 ` [PATCH 4/7] readahead: remove several readahead macros Fengguang Wu
2007-07-21 4:43 ` Fengguang Wu
2007-07-21 4:43 ` [PATCH 5/7] readahead: remove the limit max_sectors_kb imposed on max_readahead_kb Fengguang Wu
2007-07-21 4:43 ` Fengguang Wu
2007-07-21 4:43 ` [PATCH 6/7] radixtree: introduce radix_tree_scan_hole() Fengguang Wu
2007-07-21 4:43 ` Fengguang Wu
2007-07-21 5:48 ` Andrew Morton
2007-07-21 6:36 ` Fengguang Wu
2007-07-21 6:36 ` Fengguang Wu
2007-07-23 7:58 ` Nick Piggin
2007-07-23 8:04 ` Fengguang Wu
2007-07-23 8:04 ` Fengguang Wu
2007-07-23 8:12 ` Fengguang Wu [this message]
2007-07-23 8:12 ` Fengguang Wu
2007-07-21 4:43 ` [PATCH 7/7] readahead: basic support of interleaved reads Fengguang Wu
2007-07-21 4:43 ` Fengguang Wu
2007-07-21 7:24 ` Rusty Russell
2007-07-21 7:57 ` Fengguang Wu
2007-07-21 7:57 ` Fengguang Wu
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=385179010.25899@ustc.edu.cn \
--to=wfg@mail.ustc.edu.cn \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.