Re: GEOM/vinum compatibility (was: vinum lock panic at startup-current)
On Sat, Aug 09, 2003 at 06:38:51AM +0200, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey" > writes: > > >> and it seems that vinum does not respect the D_NOGIANT flag which > >> GEOM recently started setting. > > > >Probably because it didn't know about it. As I've said before, it > >would be nice to be informed about the changes you're making, > >particularly given your stated intention of doing no work on Vinum. > > I had the choice between supporting sos@ effort to de-Giantize ATA > or wait for the non-maintainer of vinum to possibly react to his email Come on.. a bit of politeness goes a long way.. > so I chose the former as being more beneficial to the project. W/ -- | / o / /_ _ |/|/ / / /( (_) Bulte [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
GEOM/vinum compatibility (was: vinum lock panic at startup -current)
On Friday, 8 August 2003 at 15:24:09 +0200, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes: > >> Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198 > > Ok, then I think I know what it is. > > Vinum appearantly does not go through SPECFS but rather calls into > the disk device drivers directly. That is a pretty wrong thing to > do, It used to be the standard. What's the issue? > and it seems that vinum does not respect the D_NOGIANT flag which > GEOM recently started setting. Probably because it didn't know about it. As I've said before, it would be nice to be informed about the changes you're making, particularly given your stated intention of doing no work on Vinum. Could you please give details (privately if you want, but I think this could be of interest to other people too). Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: GEOM/vinum compatibility (was: vinum lock panic at startup-current)
In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey" writes: >> and it seems that vinum does not respect the D_NOGIANT flag which >> GEOM recently started setting. > >Probably because it didn't know about it. As I've said before, it >would be nice to be informed about the changes you're making, >particularly given your stated intention of doing no work on Vinum. I had the choice between supporting sos@ effort to de-Giantize ATA or wait for the non-maintainer of vinum to possibly react to his email so I chose the former as being more beneficial to the project. >Could you please give details (privately if you want, but I think this >could be of interest to other people too). See sys/fs/specfs/specfs_vnops.c, that is probably faster. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
