> > 1. Much faster, thanks to a major optimization of the way fork-exec is
> > implemented.
>
> IIRC, that feature's effects on the scheduler were not considered properly,
> and you could get all kinds of undesired scheduling behavior under 2.4.3,
> such as unresponsive processes and the like, and Linus reverted it in 2.4.4.
Actually 2.4.4 introduced this change, and it's been reverted in
2.4.5-pre1.
I really don't understand how come it created problems though. Can
anyone explain it? Why would user-level processes care about
scheduling intricacies in the kernel? How is fork implemented in other
Unix variants -- is it done the slow way in all of them?
> > 2. Networking is much faster too, thanks to the "zero-copy-networking".
As far as I understand, in order to benefit from zero-copy networking,
your NIC driver needs to support it, and only a couple of drivers
support it as of this moment.
--
Alex Shnitman <[EMAIL PROTECTED]>
http://alexsh.hectic.net/ UIN 188956
PGP 0xEC5D619D / E1 F2 7B 6C A0 31 80 28 63 B8 02 BA 65 C7 8B BA
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
