public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Adrian Bunk <bunk@fs.tum.de>
Subject: Re: 2.6.1-rc1-tiny2
Date: Tue, 06 Jan 2004 18:08:03 +1100	[thread overview]
Message-ID: <3FFA5ED3.6040000@cyberone.com.au> (raw)
In-Reply-To: <20040106064607.GB18208@waste.org>


Matt Mackall wrote:

>On Tue, Jan 06, 2004 at 05:33:58PM +1100, Nick Piggin wrote:
>
>>
>>Matt Mackall wrote:
>>
>>
>>>This is the fourth release of the -tiny kernel tree. The aim of this
>>>tree is to collect patches that reduce kernel disk and memory
>>>footprint as well as tools for working on small systems. Target users
>>>are things like embedded systems, small or legacy desktop folks, and
>>>handhelds.
>>>
>>>
>>Have you considered Adrian Bunk's CPU selection rationalisation work?
>>
>
>Vaguely aware of it.
>

Basically, because the types of x86 cpus are only partially ordered,
and a the CPU selection somehow tries to follow the rule "this CPU or
higher", there ends up being a bit of stuff included which doesn't
need to be. Not sure what the savings add up to though...

>
>>The last argument I heard against it was that there is lower hanging
>>fruit for size reduction. You seem to have got a lot of that.
>>
>
>Yes, a fair amount. Btw, what's the size differential for piggin-sched
>vs mainline?
>

Very little, I think my sched.o is about 40 bytes bigger on UP. Its about
4K bigger for SMP, but thats with quite a bit of init stuff to set up the
sched domains. It also does HT scheduling, and some more of that could be
ifdefed I guess (its already 1-2K smaller than Ingo's shared runqueues).

If you're talking about my interactivity stuff, then that is very little
difference as well, maybe a few tens of bytes smaller. The scheduler is
pretty lean.



  reply	other threads:[~2004-01-06  7:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06  5:48 2.6.1-rc1-tiny2 Matt Mackall
2004-01-06  6:33 ` 2.6.1-rc1-tiny2 Nick Piggin
2004-01-06  6:46   ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-06  7:08     ` Nick Piggin [this message]
2004-01-10  0:46       ` 2.6.1-rc1-tiny2 Adrian Bunk
2004-01-10  0:50         ` [0/4] better i386 CPU selection Adrian Bunk
2004-01-10  0:52         ` [1/4] " Adrian Bunk
2004-01-10 11:04           ` Wichert Akkerman
2004-01-11  3:13             ` Adrian Bunk
2004-01-14 20:49               ` [-mm patch] " Adrian Bunk
2004-01-16 19:15           ` [1/4] " cliff white
2004-01-16 19:32             ` Richard B. Johnson
2004-01-17  0:01               ` Andrew Morton
2004-01-17  2:57                 ` Adrian Bunk
2004-01-19 15:14                   ` John Stoffel
2004-01-19 23:42                     ` Nick Piggin
2004-01-17  2:15               ` Adrian Bunk
2004-01-17  9:13                 ` Robert Schwebel
2004-01-20 22:10                   ` Adrian Bunk
2004-01-20 22:31                     ` Richard B. Johnson
2004-01-20 22:47                     ` George Anzinger
2004-01-17 10:01                 ` aeriksson
2004-01-10  0:57         ` [2/4] move "struct movsl_mask movsl_mask" to usercopy.c Adrian Bunk
2004-01-10  0:57         ` [3/4] proof of concept: make arch/i386/kernel/cpu/Makefile CPU specific Adrian Bunk
2004-01-10  0:58         ` [4/4] proof of concept: make arch/i386/kernel/cpu/mtrr/Makefile " Adrian Bunk
2004-01-10 22:14         ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-12  2:20           ` 2.6.1-rc1-tiny2 Nick Piggin
2004-01-07 14:06 ` 2.6.1-rc1-tiny2 Jens Axboe
2004-01-07 18:50   ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-07 19:27     ` 2.6.1-rc1-tiny2 Mitchell Blank Jr
2004-01-07 20:10       ` 2.6.1-rc1-tiny2 Matt Mackall
2004-01-07 21:41         ` 2.6.1-rc1-tiny2 Trond Myklebust
2004-01-07 21:10     ` 2.6.1-rc1-tiny2 Jens Axboe
2004-01-07 21:30       ` 2.6.1-rc1-tiny2 Matt Mackall

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=3FFA5ED3.6040000@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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