public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: GCS <gcs@lsc.hu>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@osdl.org>,
	helgehaf@aitel.hist.no, linux-kernel@vger.kernel.org
Subject: Re: 2.6.1-mm5 dies booting, possibly network related
Date: Tue, 20 Jan 2004 21:52:01 +0100	[thread overview]
Message-ID: <20040120205201.GA17026@lsc.hu> (raw)
In-Reply-To: <200401201853.i0KIrS6Z025026@turing-police.cc.vt.edu>

On Tue, Jan 20, 2004 at 01:53:28PM -0500, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> On Tue, 20 Jan 2004 10:23:02 PST, Andrew Morton said:
> 
> > So yes, whatever compiler you are using, turn off CONFIG_REGPARM - it is
> > still very experimental.
 It's not CONFIG_REGPARM :-(, I have turned it off, recompiled, reboot
-> same effect (it seems the list dropped my mail with bootlog, should I
resend it to the list with gzip compression?).
 If someone can help me what patches should I revert, I would be happy
to help OTOH.

> > (And of dubious value - it only saved me 0.6% of program text).
 It was for experiencing only, but I see it's not for real value. :-|

> I wonder if this is because the x86 architecture is relatively
> register-starved,
 I have started on Sun's SparcStaion (LX actually), and I like RISC
processors much more since then. :-)

> and as a result, we pass the parameters in registers, but the
> first thing the function has to do is store half of them on the stack so it has
> enough free registers to work with.  If this is the case then regparm(1) or
> regparm(2) may do better/worse by changing how much register pressure the
> function starts off with.
 Yup, that can be the reason why Andrew saw only 0.6% save on program text.

Cheers,
GCS

  reply	other threads:[~2004-01-20 21:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20  8:05 2.6.1-mm5 Andrew Morton
2004-01-20 10:51 ` 2.6.1-mm5 dies booting, possibly network related Helge Hafting
     [not found]   ` <20040120175408.GA12805@lsc.hu>
2004-01-20 18:23     ` Andrew Morton
2004-01-20 18:53       ` Valdis.Kletnieks
2004-01-20 20:52         ` GCS [this message]
2004-01-20 22:12       ` Helge Hafting
2004-01-21  9:35       ` 2.6.1-mm5 dies booting, possibly ipv6 related Helge Hafting
2004-01-21  9:29         ` Andrew Morton
2004-01-21 13:25           ` Helge Hafting
2004-01-21 14:28         ` GCS
2004-01-21 15:43           ` GCS
2004-01-20 11:14 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 16:37   ` 2.6.1-mm5 Andrew Morton
2004-01-20 11:35 ` 2.6.1-mm5 Christoph Hellwig
2004-01-20 13:20 ` [patch] 2.6.1-mm5: compile error with IDE legacy driver Adrian Bunk
2004-01-20 15:37   ` Bartlomiej Zolnierkiewicz
2004-01-20 13:45 ` [PATCH] missing space in printk message (was Re: 2.6.1-mm5) Sean Neakums
2004-01-20 13:54   ` Vojtech Pavlik
2004-01-20 14:09     ` Sean Neakums
2004-01-20 16:03 ` 2.6.1-mm5 [Compile error] Tim Cambrant
2004-01-20 16:08 ` 2.6.1-mm5 (compile stats) John Cherry
2004-01-20 21:57   ` Adrian Bunk
2004-01-20 22:15     ` John Cherry
2004-01-20 22:27       ` Adrian Bunk
2004-01-20 22:50         ` John Cherry
2004-01-20 18:30 ` 2.6.1-mm5 Mike Fedyk
2004-01-20 18:36   ` 2.6.1-mm5 Andrew Morton
2004-01-21  0:10 ` I2C sensors error (Re: 2.6.1-mm5) Zack Winkles
2004-01-21  0:34   ` Greg KH
2004-01-21  6:38 ` 2.6.1-mm5 - oops during network initialization Valdis Kletnieks
2004-01-21  8:31   ` Catalin BOIE
2004-01-21 15:46     ` GCS
2004-01-21 16:59       ` Valdis.Kletnieks
2004-01-21 18:58         ` Andrew Morton
2004-01-21 19:35           ` Valdis.Kletnieks
2004-01-21 23:19             ` GCS
2004-01-22 21:54             ` Valdis.Kletnieks
2004-01-22  9:35       ` Catalin BOIE

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=20040120205201.GA17026@lsc.hu \
    --to=gcs@lsc.hu \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@osdl.org \
    --cc=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.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