Re: Reminder: NET_NEEDS_GIANT, debug.mpsafenet going away in 7.0

On Tue, 2007-07-17 at 13:21 +0100, Robert Watson wrote:
Dear all:

This is a reminder e-mail that, in the very near future, Giant compatibility
shims for network protocols will be removed. These shimmed allowed Giant to
be re-enabeld over the network stack as a result of linking in a service that
required Giant (now all removed), or by setting the debug.mpsafenet variable
to 1. This means that the following will no longer be present:

debug.mpsafenet sysctl
debug_mpsafenet global variable
NET_NEEDS_GIANT()
NET_LOCK_GIANT(), NET_UNLOCK_GIANT(), NET_ASSERT_GIANT()
NET_CALLOUT_MPSAFE

All instances of NET_{LOCK,UNLOCK,ASSERT}_GIANT() will be removed as they will
no be no-ops.

Ehrm ... i am not 100% sure here but what will this mean for those of us
running qemu on 7.x systems ... if i recall correctly qemu requires aio
for at least DMA which on 6.x at least still issues below warning when
kldloaded:

WARNING: Network stack Giant-free, but aio requires Giant.
Consider adding 'options NET_WITH_GIANT' or setting
debug.mpsafenet=0

Does this removal of debug.mpsafenet mean that aio on CURRENT is now
GIANT free .. or does this mean that we'll be seeing problems with qemu
on CURRENT ?

--
Pascal Hofstee


_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Running the network stack without Giant -- change in default coming
    ... > to allow the network stack to run in parallel on multiple processors ... > currently unsafe without the Giant lock turned on. ... > configuration for testing out the impact of disabling Giant on MP ...
    (freebsd-current)
  • Running the network stack without Giant -- what to try and when
    ... As many of you have seen from status reports, e-mails, bug reports, etc, ... the FreeBSD Project has been working for some time on getting the network ... without the Giant lock, and we're ready for more people to start running ... - While we've been doing pretty heavy testing in MPSAFE configurations, ...
    (freebsd-current)
  • Removing NET_NEEDS_GIANT: first patch
    ... This source code declaration was used by optionally compiled components to declare a strict requirement for Giant, and forced Giant over the entire network stack. ... retrieving revision 1.13 ... diff -u -r1.13 amrr.c ...
    (freebsd-arch)
  • Removing NET_NEEDS_GIANT: first patch
    ... This source code declaration was used by optionally compiled components to declare a strict requirement for Giant, and forced Giant over the entire network stack. ... retrieving revision 1.13 ... diff -u -r1.13 amrr.c ...
    (freebsd-current)
  • Re: Reminder: NET_NEEDS_GIANT, debug.mpsafenet going away in 7.0
    ... This is a reminder e-mail that, in the very near future, Giant compatibility ... shims for network protocols will be removed. ... running qemu on 7.x systems ... ... Network stack Giant-free, but aio requires Giant. ...
    (freebsd-current)