From: "Ihar \"Philips\" Filipau" <filia@softhome.net>
To: Mike Fedyk <mfedyk@matchmail.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 13:57:12 +0200 [thread overview]
Message-ID: <3F23BE18.5000600@softhome.net> (raw)
In-Reply-To: <20030725204613.GB1686@matchmail.com>
Mike Fedyk wrote:
>
> Vanilla will be what people put into it. And I have seen more messages from
> embedded people complaining, than actually doing and submitting patches for
> merging.
>
> So the embedded trees are a deep fork huh? Did you or anyone else do
> anything to merge during 2.5?!
>
> And now you see why there is a "deep" fork...
>
Real-time stuff is a must - something like RTAI.
Things like Linux Trace Toolkit - soone or later you have to start
using them to tune performace.
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.
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!
Kernel heavily tuned for servers and workstations (read - modern PCs).
At my previous position company was using kernel prepared by Karim
Yaghmour and right now we using kernels from MontaVista.
Far from vanillas.
> embedded people complaining
Sure complaining.
For some reasons all "improvements" to kernel had lead to increase of
kernel size, not decrease. Strange, isn't it?
next prev parent reply other threads:[~2003-07-27 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d2nx.4QV.15@gated-at.bofh.it>
[not found] ` <dbTZ.5Z5.19@gated-at.bofh.it>
2003-07-25 15:37 ` [uClinux-dev] Kernel 2.6 size increase - get_current()? 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 [this message]
2003-07-27 13:05 ` Francois Romieu
[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
[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 ` Ihar "Philips" Filipau
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=3F23BE18.5000600@softhome.net \
--to=filia@softhome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.