Re: FreeBSD vs. OSX
From: jpd (read_the_sig_at_do.not.spam.it)
Date: 12/24/03
- Next message: Robert Downes: "Re: MS drivers on Freebsd"
- Previous message: Lowell Gilbert: "Re: an address specified as 1.2.3.4/24{128,35-55,89} doesn't appear to actuall ywork?"
- In reply to: Eric Masson: "Re: FreeBSD vs. OSX"
- Next in thread: jpd: "Re: FreeBSD vs. OSX"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 24 Dec 2003 16:06:43 +0000 (UTC)
In article <86llp2wcmy.fsf@t39bsdems.interne.kisoft-services.com>,
Eric Masson wrote:
> You're right, some oses solve this issue by placing drivers in userland
> and just keeping basic functions in kernel.
Some things you _have_ to run at quite high privileges. But you really
want to move things to where they can't break other things as much as
possible.
> Drivers (hardware, filesystems, protocols) can then be debugged with
> userland tools and won't crash the whole system if they fail.
>
> Take a look at the hurd or Mach for further information, FreeBSD has
> available patches that help running the ip stack in userland, iirc Dfly
> will investigate in this area for filesystems.
For example, FreeBSD ppp handles the control stuff --the most brittle
stuff, but not much of it, fortunately-- in userland, but has the much
simpler bulk of data transport handled by netgraph, in kernel space.
Running the entirety of the IP stack in userland is an interesting
excercise but I doubt it'll see much practical use: it just adds two
more context switches to the send and receive chains. I wonder what
mechanisms are available to circumvent that overhead.
-- j p d (at) d s b (dot) t u d e l f t (dot) n l .
- Next message: Robert Downes: "Re: MS drivers on Freebsd"
- Previous message: Lowell Gilbert: "Re: an address specified as 1.2.3.4/24{128,35-55,89} doesn't appear to actuall ywork?"
- In reply to: Eric Masson: "Re: FreeBSD vs. OSX"
- Next in thread: jpd: "Re: FreeBSD vs. OSX"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|