mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Sam Ravnborg <sam@ravnborg.org>, Adrian Bunk <bunk@kernel.org>,
	linux arch <linux-arch@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH] prepare kconfig inline optimization for all architectures
Date: Sun, 27 Apr 2008 16:26:06 -0700	[thread overview]
Message-ID: <20080427162606.3dd82c0c@laptopd505.fenrus.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0804271118500.2896@woody.linux-foundation.org>

On Sun, 27 Apr 2008 11:24:28 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> 
> 
> On Sun, 27 Apr 2008, Christoph Hellwig wrote:
> > 
> > As Linus mentioned the hint doesn't make any sense because gcc will
> > get it wrong anyway.  In fact when you look at kernel code it tends
> > to inline the everything and the kitchensink as long as there's just
> > one caller and this bloat the stack but doesn't inline where it
> > needs to.  Better don't try to mess with that and do it explicit.
> 
> The thing is, the "inline" vs "always_inline" thing _could_ make
> sense, but sadly doesn't much.
> 
> Part of it is that gcc imnsho inlines too aggressively anyway in the 
> absense of "inline",


yup.. but this patch doesn't change that... the "no inline keyword" case
is totally unaffected...


(actually, other than some obscure commandline options, the only sane way to
avoid gcc doing this too agressive is using -Os)

-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  parent reply	other threads:[~2008-04-27 23:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 10:51 Sam Ravnborg
2008-04-27 11:31 ` Adrian Bunk
2008-04-27 11:56   ` Sam Ravnborg
2008-04-27 12:36     ` Ingo Molnar
2008-04-27 12:49       ` Ingo Molnar
2008-04-27 17:06   ` Linus Torvalds
2008-04-27 17:22     ` Adrian Bunk
2008-04-27 17:32       ` Linus Torvalds
2008-04-27 17:47         ` Adrian Bunk
2008-04-27 18:00           ` Christoph Hellwig
2008-04-27 18:09             ` Sam Ravnborg
2008-04-27 18:14               ` Christoph Hellwig
2008-04-27 18:24                 ` Linus Torvalds
2008-04-27 18:32                   ` Christoph Hellwig
2008-04-27 19:36                   ` Ingo Molnar
2008-04-27 19:49                     ` Adrian Bunk
2008-04-27 23:26                   ` Arjan van de Ven [this message]
2008-04-27 23:36                     ` Linus Torvalds
2008-04-27 23:41                       ` Ingo Molnar
2008-04-27 18:31                 ` Sam Ravnborg
2008-04-27 18:36                   ` Christoph Hellwig
2008-04-27 18:11           ` Linus Torvalds
2008-04-27 18:25             ` Christoph Hellwig
2008-04-27 18:30               ` Linus Torvalds
2008-04-27 18:41             ` Adrian Bunk
2008-04-27 18:57               ` Linus Torvalds
2008-04-27 20:51           ` Mike Galbraith
2008-04-27 17:57         ` Christoph Hellwig
2008-04-27 17:40       ` Matthew Wilcox
2008-04-27 17:59         ` Adrian Bunk

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=20080427162606.3dd82c0c@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=bunk@kernel.org \
    --cc=davem@davemloft.net \
    --cc=hch@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®