Date: Fri, 15 Dec 2000 12:06:10 -0600 From: "Michael C . Wu" <keichii@iteration.net> To: "Koster, K.J." <K.J.Koster@kpn.com> Cc: 'Wes Peters' <wes@softweyr.com>, Jonas Bulow <jonas.bulow@servicefactory.se>, hackers@FreeBSD.ORG Subject: Re: kqueue microbenchmark results Message-ID: <20001215120610.A40179@peorth.iteration.net> In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D7ABF@l04.research.kpn.com>; from K.J.Koster@kpn.com on Fri, Dec 15, 2000 at 04:36:57PM %2B0100 References: <59063B5B4D98D311BC0D0001FA7E4522026D7ABF@l04.research.kpn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 15, 2000 at 04:36:57PM +0100, Koster, K.J. scribbled: | > http://linuxtoday.com/news_story.php3?ltsn=2000-12-09-013-20-NW-GN-KN | > Device drivers in Perl. What a spectacularly bad idea. ;^) | That's what people used to say about writing kernels in C. There is a difference between (compiling C device driver module and loading into an ASM kernel) and (interpreting a Perl device driver that uses userland tools.) Confusing kernel and userland results in WIN32 API+Integrated Exchange Server crashes. Or think of the linux kernel httpd project. I cannot think of that many reasons against keeping kernel in kernel, and userland in userland (if any). Latency, locking, security, and performance all goes agains this. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001215120610.A40179>