FreeLists / openbeosnetteam / [openbeosnetteam] Re: Unloading modules...

["David Reid" <dreid@xxxxxxxxxxxx>]

> David wrote:
>
> > Big issues:
> > - thread safety. We can easily be stopping and removing modules as other
> > modules are trying to call them. This would be v.bad
>
> Here we could take profit of the ref count feature of get/put_module().
> Instead of doing only one get_module() the first time we need a module,
> we could call it *each* time. That way, the kernel will do ref count for
> us.
>
> But it'll need to take care of any first_time startup code, like
> core->start() for example...
> It could be really tricky!

Erm, that's not the issue at all...

>
> > - this can't be done via a socket, as a socket needs functions
> > to be called in modules. Therefore this should be done via a
> > sysctl call once we get that integrated into the kernel
>
> Hum, what about a dedicated /dev/net/stack driver ioctl() ?
> It's there. We can open() the driver *without* using a socket...
> AFAIR, there is already some NET_STACK_RESTART opcode, commented out,
> in the net_stack_control() code...

Unless I've missed soemthing here, to use ioctl we need a socket, and the
existance of a socket is what I'm trying to avoid...

We'll just use sysctl into the new kernel.

david