linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Will L Givens" <wlgivens@gmail.com>
To: 'Michael Cree' <mcree@orcon.net.nz>
Cc: linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
	'Matt Turner' <mattst88@gmail.com>
Subject: RE: Will's kernel compilation error
Date: Tue, 16 Mar 2010 17:42:02 -0500	[thread overview]
Message-ID: <007801cac559$e798c330$b6ca4990$@com> (raw)
In-Reply-To: <4AB85842-79DF-412F-833C-4B784353A1F5@orcon.net.nz>


> The patch is not suitable, IMHO, for the kernel as it stands.  Some of
> us prefer the small-data model as we must boot off a slow medium that
> is supported by SRM.  Using large-data results in a larger code size.
> 
> It would be nice if the build system could detect the need for the
> large-data model before compilation but I can't see how to do that
> without actually compiling the kernel.
> 
> Therefore I suggest a kernel config item be added to optionally remove
> the -msmall-data compiler option for those who are building kernels
> with data areas greater than 64kB.  I'll drum up a patch later today.
> 
> Cheers
> Michael.

Actually I added several modules into the kernel (raid0/1, router protocols,
and subsystem for TV cards)and it was about 100KB smaller. If push came to
shove, you could simply strip the symbols from the kernel (strip -s vmlinux)
and modules and use gzip -9 (done it in the past and it works fine). Another
thing, how could 2MB make that big of a different on boot time? I used to
use an old 50MB AT drive on my UP2000 (OS installed to 2 IDE drives via a
non-bootable Promise card)and it read at 1MB/s. So, at worst, you're talking
about maybe a 1 to 2 second difference?

Just tested it on my currently modules, went from 35MB to 19MB... not too
shabby.


  reply	other threads:[~2010-03-16 22:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 23:09 Will's kernel compilation error Matt Turner
2010-03-15 23:21 ` Will L Givens
2010-03-16  2:34 ` Will L Givens
2010-03-16  4:25   ` Matt Turner
2010-03-16  5:50 ` Will L Givens
2010-03-16  7:08   ` Michael Cree
2010-03-16 16:17     ` Will L Givens
2010-03-16 17:09     ` Will L Givens
2010-03-16 17:32     ` Will L Givens
2010-03-16 18:25   ` Thorsten Kranzkowski
2010-03-16 18:38     ` Will L Givens
2010-03-16 21:23     ` Will L Givens
2010-03-16 21:39       ` Matt Turner
2010-03-16 22:05         ` Michael Cree
2010-03-16 22:42           ` Will L Givens [this message]
2010-03-16 19:34 ` Raúl Porcel
2010-03-17  7:34   ` Michael Cree
2010-03-17  8:55     ` Will L Givens
2010-03-17  9:13       ` Justin P. Mattock

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='007801cac559$e798c330$b6ca4990$@com' \
    --to=wlgivens@gmail.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=mcree@orcon.net.nz \
    /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;
as well as URLs for NNTP newsgroup(s).