All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, Milton Miller <miltonm@bga.com>,
	Ingo Molnar <mingo@redhat.com>,
	Andres Salomon <dilinger@queued.net>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 3/3] x86: OLPC: speed up device tree creation during boot (v2)
Date: Thu, 18 Nov 2010 22:02:15 +1100	[thread overview]
Message-ID: <1290078135.22575.4.camel@concordia> (raw)
In-Reply-To: <20101118083420.GC26398@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]

On Thu, 2010-11-18 at 09:34 +0100, Ingo Molnar wrote:
> * H. Peter Anvin <hpa@zytor.com> wrote:
> 
> > On 11/14/2010 11:02 PM, Ingo Molnar wrote:
> > > 
> > > * H. Peter Anvin <hpa@zytor.com> wrote:
> > > 
> > >> What?  What is wrong with static variables in functions?  It really doesn't seem 
> > >> to be a good idea to make them file-scope if they don't need to be.
> > > 
> > > They are very easy to overlook and mix up with regular stack variables and i've seen 
> > > (and introduced myself) a number of bugs due to them.
> > > 
> > > They also often are used in buggy ways (with SMP not taken into consideration), so 
> > > overlooking them during review compounds their negative effects. Putting them in 
> > > front of the function isnt a big deal in exchange.
> > > 
> > > There are people who never overlook them (like yourself), but my brain is wired up 
> > > differently.
> > > 
> > 
> > However, I have to vehemently object to putting them in a wider scope
> > than is otherwise necessary.  I agree that static variables should be
> > used sparsely if at all (there really are vary few uses of them that are
> > valid), but putting them in a larger scope screams "I'm used in more
> > than one function", and that is *not* a good thing.
> 
> That's why we sometimes use the (imperfect) compromise to put them in front of that 
> function, not at the top of the file.
> 
> Look at the general balance of hardship: very little harm is done (it's not a big 
> deal if a variable is only used in a single function) but having it with local 
> variables can be _really_ harmful - for example i overlooked them when i reviewed 
> this patch. I dont like important details obscured - i like them to be apparent. 
> Again, this is something that some people can parse immediately on the visual level 
> - me and many others cannot.

What about:

int foo(void)
{
	static int bar;

	struct thing_struct *thing;
	int other_var;
	char *p;

	...
}

I think the visual wrongness of that formatting would be enough for me
to stop and look twice. Though I guess it doesn't work if you have few,
or no other variables other than the statics to declare.

cheers


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <michael-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>
To: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Milton Miller <miltonm-ogEGBHC/i9Y@public.gmane.org>,
	Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Andres Salomon <dilinger-pFFUokh25LWsTnJN9+BGXg@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Subject: Re: [PATCH 3/3] x86: OLPC: speed up device tree creation during boot (v2)
Date: Thu, 18 Nov 2010 22:02:15 +1100	[thread overview]
Message-ID: <1290078135.22575.4.camel@concordia> (raw)
In-Reply-To: <20101118083420.GC26398-X9Un+BFzKDI@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2277 bytes --]

On Thu, 2010-11-18 at 09:34 +0100, Ingo Molnar wrote:
> * H. Peter Anvin <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org> wrote:
> 
> > On 11/14/2010 11:02 PM, Ingo Molnar wrote:
> > > 
> > > * H. Peter Anvin <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org> wrote:
> > > 
> > >> What?  What is wrong with static variables in functions?  It really doesn't seem 
> > >> to be a good idea to make them file-scope if they don't need to be.
> > > 
> > > They are very easy to overlook and mix up with regular stack variables and i've seen 
> > > (and introduced myself) a number of bugs due to them.
> > > 
> > > They also often are used in buggy ways (with SMP not taken into consideration), so 
> > > overlooking them during review compounds their negative effects. Putting them in 
> > > front of the function isnt a big deal in exchange.
> > > 
> > > There are people who never overlook them (like yourself), but my brain is wired up 
> > > differently.
> > > 
> > 
> > However, I have to vehemently object to putting them in a wider scope
> > than is otherwise necessary.  I agree that static variables should be
> > used sparsely if at all (there really are vary few uses of them that are
> > valid), but putting them in a larger scope screams "I'm used in more
> > than one function", and that is *not* a good thing.
> 
> That's why we sometimes use the (imperfect) compromise to put them in front of that 
> function, not at the top of the file.
> 
> Look at the general balance of hardship: very little harm is done (it's not a big 
> deal if a variable is only used in a single function) but having it with local 
> variables can be _really_ harmful - for example i overlooked them when i reviewed 
> this patch. I dont like important details obscured - i like them to be apparent. 
> Again, this is something that some people can parse immediately on the visual level 
> - me and many others cannot.

What about:

int foo(void)
{
	static int bar;

	struct thing_struct *thing;
	int other_var;
	char *p;

	...
}

I think the visual wrongness of that formatting would be enough for me
to stop and look twice. Though I guess it doesn't work if you have few,
or no other variables other than the statics to declare.

cheers


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 192 bytes --]

_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

  reply	other threads:[~2010-11-18 11:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12  5:45 [PATCH 3/3] x86: OLPC: speed up device tree creation during boot (v2) Andres Salomon
2010-11-12  5:45 ` Andres Salomon
2010-11-12  7:48 ` Milton Miller
2010-11-12  7:48   ` Milton Miller
2010-11-12  8:27   ` Andres Salomon
2010-11-12  8:27     ` Andres Salomon
2010-11-14  9:50     ` Ingo Molnar
2010-11-15  4:21       ` H. Peter Anvin
2010-11-15  4:21         ` H. Peter Anvin
2010-11-15  7:02         ` Ingo Molnar
2010-11-15  7:02           ` Ingo Molnar
2010-11-15 17:43           ` H. Peter Anvin
2010-11-15 17:43             ` H. Peter Anvin
2010-11-17  6:12             ` [PATCH 3/3] x86: OLPC: speed up device tree creation during boot (v3) Andres Salomon
2010-11-17  6:12               ` Andres Salomon
2010-11-29 23:39               ` [PATCH 3/3] x86: OLPC: speed up device tree creation during boot (v4) Andres Salomon
2010-12-16  2:58                 ` [tip:x86/olpc] x86, olpc: Speed up device tree creation during boot tip-bot for Andres Salomon
2010-11-18  8:34             ` [PATCH 3/3] x86: OLPC: speed up device tree creation during boot (v2) Ingo Molnar
2010-11-18  8:34               ` Ingo Molnar
2010-11-18 11:02               ` Michael Ellerman [this message]
2010-11-18 11:02                 ` Michael Ellerman
2010-11-18 15:04                 ` H. Peter Anvin
2010-11-18 15:04                   ` H. Peter Anvin
2010-11-18 17:41                   ` Andres Salomon
2010-11-18 17:41                     ` Andres Salomon
2010-11-18 17:48                     ` H. Peter Anvin
2010-11-18 17:48                       ` H. Peter Anvin
2010-11-19 20:24                       ` Andres Salomon
2010-11-19 20:24                         ` Andres Salomon
2010-12-23 11:57               ` Ingo Molnar

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=1290078135.22575.4.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dilinger@queued.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miltonm@bga.com \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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.