Please everyone feel free to fill in the blanks. I'll try to do it as well
as time permits.
You might also want to cross-link with the SMPTODO page.
Robert N M Watson
Computer Laboratory
University of Cambridge
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (f ... On Sat, 24 May 2008, Coleman Kane wrote: ... Please everyone feel free to fill in the blanks.... I'll try to do it as well as time permits.... I suspect fixing things like SLIP and kernel PPP are fairly trivial once tty locking is in place -- a per-softc mutex and a bit of locking in the obvious spots would likely do it without too much trouble. ... (freebsd-arch)
Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (f ... On Sat, 24 May 2008, Coleman Kane wrote: ... Please everyone feel free to fill in the blanks.... I'll try to do it as well as time permits.... I suspect fixing things like SLIP and kernel PPP are fairly trivial once tty locking is in place -- a per-softc mutex and a bit of locking in the obvious spots would likely do it without too much trouble. ... (freebsd-current)
Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (f ... On Sat, 24 May 2008, Coleman Kane wrote: ... Please everyone feel free to fill in the blanks.... I'll try to do it as well as time permits.... I suspect fixing things like SLIP and kernel PPP are fairly trivial once tty locking is in place -- a per-softc mutex and a bit of locking in the obvious spots would likely do it without too much trouble. ... (freebsd-net)