From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: linux-kernel@vger.kernel.org, WU Fengguang <wfg@mail.ustc.edu.cn>,
Andrew Morton <akpm@google.com>
Subject: Re: radix-tree.c:__lookup_slot() dead code removal
Date: Mon, 04 Dec 2006 21:18:40 +1100 [thread overview]
Message-ID: <4573F600.50306@yahoo.com.au> (raw)
In-Reply-To: <20061203170231.GA20298@janus>
Frank van Maarseveen wrote:
> Most of the code suggests that it is valid to insert a NULL item,
> possibly a zero item with pointer cast. However, in __lookup_slot()
> whether or not the slot is found seems to depend on the actual value
> of the item in one special case. But further on it doesn't make any
> difference so to remove some dead code:
>
> --- a/lib/radix-tree.c 2006-12-03 13:23:00.000000000 +0100
> +++ b/lib/radix-tree.c 2006-12-03 17:57:03.000000000 +0100
> @@ -319,9 +319,6 @@ static inline void **__lookup_slot(struc
> if (index > radix_tree_maxindex(height))
> return NULL;
>
> - if (height == 0 && root->rnode)
> - return (void **)&root->rnode;
> -
> shift = (height-1) * RADIX_TREE_MAP_SHIFT;
> slot = &root->rnode;
I would say it is not valid to insert a NULL item (because NULL
means an unsuccessful lookup, you may as well just delete the
item).
Also, I don't see how this is dead code anyway. height == 0
radix-trees are a special case and do not have a radix_tree_node
at ->rnode.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-12-04 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 17:02 radix-tree.c:__lookup_slot() dead code removal Frank van Maarseveen
2006-12-04 2:26 ` Fengguang Wu
2006-12-04 2:26 ` Fengguang Wu
2006-12-04 10:18 ` Nick Piggin [this message]
2006-12-04 10:37 ` WU Fengguang
2006-12-04 10:37 ` 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=4573F600.50306@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@google.com \
--cc=frankvm@frankvm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wfg@mail.ustc.edu.cn \
/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.