Date: Wed, 06 Dec 2000 06:49:50 -0800 From: Julian Elischer <julian@elischer.org> To: Brian Somers <brian@Awfulhak.org> Cc: smp@FreeBSD.org, archie@FreeBSD.org Subject: Re: Netgraph and SMP Message-ID: <3A2E520E.5E4444BD@elischer.org> References: <200012051902.eB5J20Y38879@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Brian Somers wrote:
>
> I don't think netgraph is the place to deal with this.
>
> kldunload should be smart enough to do several things:
>
> Look at the dependency graph that it maintains (does it?) and
> decide if there are any dependent modules. If they are, refuse
> the unload request.
I be;ieve this is already done (but am not totally sure)
>
> Inside it's own lock (preventing any other dependent modules from
> appearing), it asks the module if it's ok to unload.
>
> This is obviously more tricky than it sounds. We've got to ensure
> that if any character device entry points have been created
> (make_dev() etc), we block the relevant entry points so that we can
> ENODEV if the MOD_UNLOAD works.
but what if the process has already entered the driver?
>
> Apart from the generic cdevsw entry points and module dependencies, I
> think it's pretty much up to the module to ensure that things work -
> unless someone can think of another way that an external source can
> use the module (sysctls spring to mind).
yep
>
--
__--_|\ Julian Elischer
/ \ julian@elischer.org
( OZ ) World tour 2000
---> X_.---._/ presently in: Budapest
v
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A2E520E.5E4444BD>