FreeLists / openbeosnetteam / [openbeosnetteam] Re: Kernel move...

["David Reid" <dreid@xxxxxxxxxxxx>]

Philippe, why? Please give me reasons that make sense...

The functions that move into the kernel will never require a change of
kernel to support a new protocol, so the argument that we'd have to
rerelease the kernel isn't valid and I can't understand why you'd want to
have to mess with ioctl's and such like when we could simply have a syscall
that keeps things much simpler.

Given that much of the networking code will be in a seperate module anyway I
don't see the problem, but the advantages that I see are enormous.

david

> Nathan wrote:
> > David wrote:
> > > Why do you think they don't need a syscall? Why is the driver more
> > > extensible?
> >
> > From the point of view of the kernel, adding special cases for
> anything
> > is usually a bad idea. Also, if we were to want to update that, and
> it
> > was compiled into the kernel, we would have to re-release the kernel
> > too, which would be unfortunate. Finally, there really isn't any
> > advantage to a syscall: open() for socket() and ioctl() for the rest
> > really work just as well, without any real speed problems.
> > -Nathan
>
> I totally agree the Nathan point of view.
>
> -Philippe
>
> --
> Fortune Cookie Says:
>
> Think twice before speaking, but don't say "think think click click".
>
>
>