this isn't really a solution, because linux development will outpace you,
but have you tried building a really tight kernel?  for desktop machines,
i've gotten noticable performance gains by building a moduleless kernel
with only the minimum needed functionality.  i built custom kernels for
(unnamed registrar) and we got +10% packet throughput on linux 2.4
running an (unnamed nameserver) for (unnamed tlds).

i think there are some kernel threads that you may be able to eliminate
with a different kernel.  i don't know if you need 'em though.

- erik

On Fri Jun  9 14:58:10 CDT 2006, [EMAIL PROTECTED] wrote:
On Wed, Jun 07, 2006 at 11:19:13PM -0600, Ronald G Minnich wrote:
[...]
> >     3 ?        SN     0:00 [ksoftirqd/0]
> >     4 ?        S      0:00 [watchdog/0]
> >     5 ?        S      0:00 [migration/1]
> >     6 ?        SN     0:00 [ksoftirqd/1]
> >     7 ?        S      0:00 [watchdog/1]
> >     8 ?        S      0:00 [migration/2]
> >     9 ?        SN     0:00 [ksoftirqd/2]
> >    10 ?        S      0:00 [watchdog/2]
> >    11 ?        S      0:00 [migration/3]
> >    12 ?        SN     0:00 [ksoftirqd/3]
> >    13 ?        S      0:00 [watchdog/3]
> >    14 ?        S<     0:00 [events/0]
> >    15 ?        S<     0:00 [events/1]
> >    16 ?        S<     0:00 [events/2]
> >    17 ?        S<     0:00 [events/3]
> >    18 ?        S<     0:00 [khelper]
> >    19 ?        S<     0:00 [kthread]
> >    26 ?        S<     0:00 [kblockd/0]
> >    27 ?        S<     0:00 [kblockd/1]
> >    28 ?        S<     0:00 [kblockd/2]
> >    29 ?        S<     0:00 [kblockd/3]
> >   105 ?        S      0:00 [pdflush]
> >   106 ?        S      0:00 [pdflush]
> >   107 ?        S      0:00 [kswapd1]
> >   109 ?        S<     0:00 [aio/0]
> >   108 ?        S      0:00 [kswapd0]
> >   110 ?        S<     0:00 [aio/1]
> >   111 ?        S<     0:00 [aio/2]
> >   112 ?        S<     0:00 [aio/3]
> >   697 ?        S<     0:00 [kseriod]
> >   855 ?        S      0:00 xsrv -D 0 tcp!*!20001
> >   857 ?        S      0:00 9pserve -u tcp!*!20001
> >   864 ?        S      0:00 u9fs -a none -u root -m 65560 -p 564
> >   865 ?        S      0:00 /bin/ash
> > 
> > see how little we have running? Oh, but wait, what's all that stuff in 
> > []? It's the stuff we can't turn off. Note there is per-cpu stuff, and 
> > other junk. Note that this node has been up for five hours, and this 
> > stuff is pretty quiet(0 run time); our nodes are the quietest (in the OS 
> > interference sense) Linux nodes I have yet seen. But, that said, all 
> > this can hit you.

Reply via email to