From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Wei Yang <weiyang.kernel@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: One comment on the __release_region in kernel/resource.c
Date: Mon, 3 Oct 2011 19:24:58 +0900 [thread overview]
Message-ID: <20111003192458.14d198a3.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <CADLM8XNiaxLFRZXs4NKJmoORvED-DV0bNxPF6eHsfnLqtxw09w@mail.gmail.com>
On Sun, 2 Oct 2011 21:57:07 +0800
Wei Yang <weiyang.kernel@gmail.com> wrote:
> Dear experts,
>
> I am viewing the source code of __release_region() in kernel/resource.c.
> And I have one comment for the performance issue.
>
> For example, we have a resource tree like this.
> 10-89
> 20-79
> 30-49
> 55-59
> 60-64
> 65-69
> 80-89
> 100-279
>
> If the caller wants to release a region of [50,59], the original code will
> execute four times in the for loop in the subtree of 20-79.
>
> After changing the code below, it will execute two times instead.
>
> By using the "git annotate", I see this code is committed by Linus as the
> initial version. So don't get more information about why this code is
> written
> in this way.
>
> Maybe the case I thought will not happen in the real world?
>
> Your comment is warmly welcome. :)
>
> diff --git a/kernel/resource.c b/kernel/resource.c
> index 8461aea..81525b4 100644
> --- a/kernel/resource.c
> +++ b/kernel/resource.c
> @@ -931,7 +931,7 @@ void __release_region(struct resource *parent,
> resource_size_t start,
> for (;;) {
> struct resource *res = *p;
>
> - if (!res)
> + if (!res || res->start > start)
Hmm ?
res->start > end ?
Thanks,
-Kame
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-10-03 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 13:57 Wei Yang
2011-10-03 10:24 ` KAMEZAWA Hiroyuki [this message]
2011-10-03 11:15 ` Geert Uytterhoeven
2011-10-03 13:35 ` Wei Yang
2011-10-03 14:03 ` Geert Uytterhoeven
2011-10-03 14:24 ` Wei Yang
2011-10-04 14:17 ` Wei Yang
2011-10-03 13:30 ` Wei Yang
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=20111003192458.14d198a3.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=weiyang.kernel@gmail.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