K 10
svn:author
V 3
jhb
K 8
svn:date
V 27
2001-02-08T00:27:38.000000Z
K 7
svn:log
V 410
Don't bother with acquiring/releasing Giant around kmem_malloc() and
kmem_free() for now.  Kmem_malloc() and kmem_free() now have appropriate
assertions in place, and these checks aren't feasible until more of the
networking code is locked down.  Also, the extra assertions here should
already be caught by the WITNESS code as lock order violations should
mutex operations on Giant be reintroduced here later.

END