Andrew Gallatin wrote: > Ugh. Since it may call kmem_malloc(), UMA must hold Giant. > > This is the same problem the mbuf system has, and its what's > keeping network device drivers under Giant in 5.0. > > Both subsytems should probably have GIANT_REQUIRED at all entry > points so as to catch locking problems like this earlier.
No, they should probably be wired into machdep.c, instead. It was pretty obvious (to me) that UMA could not use the kmem primitives, if it wanted to avoid Giant, even right at the beginning of integration. I just assumed that this was known, and that it would be dealt with later, using one of several approaches. IMO, the easiest approach is mapping all physical RAM into the KVA at the start of life, and then apportioning it out from there. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
