linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ihar \"Philips\" Filipau" <filia@softhome.net>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OT: Vanilla not for embedded?! Re: Kernel 2.6 size increase - get_current()?
Date: Sun, 27 Jul 2003 16:33:46 +0200	[thread overview]
Message-ID: <3F23E2CA.7070107@softhome.net> (raw)
In-Reply-To: <dTrN.5Te.7@gated-at.bofh.it>

Francois Romieu wrote:
>>   Patches to remove mandatory (for 2.2/2.0) PCI/IDE support were pretty 
>>common too.
>>   Patch to shrink network hashes - norm of life.
>>   Patch to kill PCI names database.
>>   And this is only things I was using personally (and I remember about) 
>>in my short 4 years carrier.
> 
> Would you mind publishing the patches ?
> 

   As I already answered privately - I do have them right now.
   And those patches were not mine.
   Most of them was collected right on lkml or from digests on lwn.net.

   [ I was playing only with network code - and I was concerned with 
performance more, than with image size. And had no luck achiving 
something. ]

> 
>>   CONFIG_TINY - http://lwn.net/Articles/14186/ - got something like 
>>this merged? - so I'm the first guy in the download queue on ftp.kernel.org!
> 
> 
> See CONFIG_EMBEDDED.
> 

   Okay. I have found it.
   But I cannot find how it is used.
   I have grepped thru 2.6.0-test0 - but I can find only entries in 
defconfigs - but no mentions in .h/.c files.
   What I'm missing?

   And yes - this option doesn't work in 'make menuconfig'.

>>   For some reasons all "improvements" to kernel had lead to increase of 
>>kernel size, not decrease. Strange, isn't it?
> 
> No time for sarcasm here.
> 

   Correct me if I'm wrong.
   I was just poking around 'small is beatiful'.


P.S. To my earlier 'far from vanilla' comment (-x '.*' - to skip 
.depend/.config/etc):
$ diff -urN -x '.*' ./linux-2.4.17 \
/opt/hardhat/devkit/lsp/ibm-walnut-ppc_405/linux-2.4.17_mvl21\
| wc -l
     1128089
$
and more than 500 additional CONFIG_* parameters comparing to vanilla.


       reply	other threads:[~2003-07-27 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dcQ9.7aj.35@gated-at.bofh.it>
     [not found] ` <dcQ9.7aj.31@gated-at.bofh.it>
     [not found]   ` <dhFS.3R3.11@gated-at.bofh.it>
     [not found]     ` <dSm7.4TZ.5@gated-at.bofh.it>
     [not found]       ` <dTrN.5Te.7@gated-at.bofh.it>
2003-07-27 14:33         ` Ihar "Philips" Filipau [this message]
2003-07-27 15:08           ` CONFIG_EMBEDDED in vanilla Francois Romieu
     [not found] <dUQT.72E.5@gated-at.bofh.it>
     [not found] ` <dUQT.72E.7@gated-at.bofh.it>
     [not found]   ` <dUQT.72E.9@gated-at.bofh.it>
     [not found]     ` <dUQT.72E.11@gated-at.bofh.it>
     [not found]       ` <dUQT.72E.13@gated-at.bofh.it>
     [not found]         ` <dUQT.72E.3@gated-at.bofh.it>
2003-07-27 14:47           ` OT: Vanilla not for embedded?! Re: Kernel 2.6 size increase - get_current()? Ihar "Philips" Filipau
     [not found] <dbTZ.5Z5.19@gated-at.bofh.it>
2003-07-25 15:37 ` [uClinux-dev] " Ihar "Philips" Filipau
2003-07-25 20:46   ` OT: Vanilla not for embedded?! " Mike Fedyk
2003-07-25 20:43     ` Andre Hedrick
2003-07-27 11:57     ` Ihar "Philips" Filipau
2003-07-27 13:05       ` Francois Romieu

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=3F23E2CA.7070107@softhome.net \
    --to=filia@softhome.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).