The things is that we don't really have IPC in place for the userland version... We have IPC for the kernel using standard calls and the kernel itself :) david > If the code runs in either space, then run it in userspace if you want; > the kernel-space ability should increase performance for those who want > to be on the "bleeding" edge. > > Cool! > > --- unlyrn <unlyrn@xxxxxxxxxxxxxxx> wrote: > > > Well, in an exciting week the code now runs in kernel space, with > > all > > > modules being loaded at run time. The drivers are still the > > original > > > be ones > > > being used via the same interface as the userland stack, which does > > > > > mean > > > that our code can be built to run as either a userland application > > or > > > as the > > > kernel drivers! > > > > Excuse my ignorance on the matter, but a few queries.... > > How does integration into kernelspace affect the way users have > > control > > over > > the networking modules? > > What I mean to say is, if there is a problem, is it still possible to > > > > simply 'restart' > > the net_server? And how about stability... is it wise to move things > > into kernel > > space when they're still untested... even when they are tested? > > As much as we might like to think otherwise, there are plenty of > > situations > > when things break, and killing the kernel team is probably not a > > NiceThing[tm] > > > > Thanks, > > David Shipman > > > > > > > ===== > ======= > Frank D. Engel, Jr. > Please note my new address: fde101@xxxxxxxxx > > __________________________________________________ > Do You Yahoo!? > Yahoo! Movies - coverage of the 74th Academy Awards® > http://movies.yahoo.com/ >