Date: Wed, 21 Jul 2004 08:49:26 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: phk@phk.freebsd.dk Cc: arch@freebsd.org Subject: Re: kldunload DIAGNOSTIC idea... Message-ID: <20040721.084926.84362543.imp@bsdimp.com> In-Reply-To: <83182.1090412961@critter.freebsd.dk> References: <1090412431.7114.13.camel@builder02.qubesoft.com> <83182.1090412961@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
[[ only cc'd arch@ ]]
In message: <83182.1090412961@critter.freebsd.dk>
"Poul-Henning Kamp" <phk@phk.freebsd.dk> writes:
: >Any ideas on how network interfaces should
: >work in this?
:
: I talked with Robert briefly about this yesterday, and the problem
: there is that struct ifnet is embedded in the softc. If the softc
: had a pointer to the ifnet, then we could do something similar, but
: as long as it's embedded we're stuck.
Why is that the case? We don't detach the ifnet stuff after deleting
the softc. Why would a pointer to ifnet in the softc make this
easier?
I mean, I understand that having a pointer would insulate the size of
ifnet from the driver, but there's so many offsets in ifnet that are
encoded in the driver that doesn't seem that big a win.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040721.084926.84362543.imp>