From: David Gibson <david@gibson.dropbear.id.au>
To: Roman Zippel <zippel@linux-m68k.org>,
kbuild-devel@lists.sourceforge.net, linuxppc64-dev@ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix Kconfig performance bug
Date: Mon, 31 Oct 2005 17:55:21 +1100 [thread overview]
Message-ID: <20051031065521.GE6622@localhost.localdomain> (raw)
In-Reply-To: <20051021014955.GA12976@localhost.localdomain>
On Fri, Oct 21, 2005 at 11:49:55AM +1000, David Gibson wrote:
> On Fri, Oct 21, 2005 at 02:46:30AM +0200, Roman Zippel wrote:
> > Hi,
> >
> > On Thu, 20 Oct 2005, David Gibson wrote:
> >
> > > When doing its recursive dependency check, scripts/kconfig/conf uses
> > > the flag SYMBOL_CHECK_DONE to avoid rechecking a symbol it has already
> > > checked. However, that flag is only set at the top level, so if a
> > > symbol is first encountered as a dependency of another symbol it will
> > > be rechecked every time it is encountered until it's encountered at
> > > the top level.
> >
> > You're correct, the check does too much.
> >
> > > Index: working-2.6/scripts/kconfig/symbol.c
> > > ===================================================================
> > > --- working-2.6.orig/scripts/kconfig/symbol.c 2005-10-20 12:40:45.000000000 +1000
> > > +++ working-2.6/scripts/kconfig/symbol.c 2005-10-20 12:41:43.000000000 +1000
> > > @@ -758,6 +758,8 @@
> > > out:
> > > if (sym2)
> > > printf(" %s", sym->name);
> > > + else
> > > + sym->flags |= SYMBOL_CHECK_DONE;
> > > sym->flags &= ~SYMBOL_CHECK;
> > > return sym2;
> > > }
> >
> > Actually this way it becomes redundant with SYMBOL_CHECKED, could you
> > merge these two flags? The above check would be also probably better:
>
> Ok, done. There is now only SYMBOL_CHECKED (seemed a clearer name to
> me), but it's semantics are like those of SYMBOL_CHECK_DONE were.
>
> > if (sym2) {
> > printf(" %s", sym->name);
> > if (sym2 == sym) {
> > printf("\n");
> > sym2 = NULL;
> > }
> > }
> >
> > So that this check will stop when it hits the start symbol and continue
> > looking for more dependency problems, which is I think I intended with the
> > original code.
>
> Erm.. ok. I don't entirely understand the intent of this is, but
> applied anyway.
>
> > > Index: working-2.6/scripts/kconfig/zconf.y
> > > ===================================================================
> > > --- working-2.6.orig/scripts/kconfig/zconf.y 2005-10-20 12:40:45.000000000 +1000
> > > +++ working-2.6/scripts/kconfig/zconf.y 2005-10-20 12:41:43.000000000 +1000
> > > @@ -495,10 +495,9 @@
> > > exit(1);
> > > menu_finalize(&rootmenu);
> > > for_all_symbols(i, sym) {
> > > +/* fprintf(stderr, "Checking %s...\n", sym->name); */
> >
> > One "quilt refresh" missing? :-)
>
> Oops. Something like that.
>
> Oh.. one caveat, the diffs I have here to zconf.tab.c_shipped are
> direct edits to match zconf.y - I didn't regenerate the file with
> bison. I've done that to getting a whole lot of irrelevant changes in
> the patch because I'm using a different version of bison to that used
> for the existing zconf.tab.[ch]_shipped
>
> Anyway, revised version below:
Now that 2.6.14 is out, do you intend to pass this patch on to Linus?
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/people/dgibson
prev parent reply other threads:[~2005-10-31 6:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 3:23 [PATCH] Fix Kconfig performance bug David Gibson
2005-10-21 0:46 ` Roman Zippel
2005-10-21 1:49 ` David Gibson
2005-10-31 6:55 ` David Gibson [this message]
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=20051031065521.GE6622@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=zippel@linux-m68k.org \
/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.