>no, that's OK, because MLGET either attaches a MCLBYTES-sized cluster
>to the mbuf or doesn't set the M_EXT flag.
>M_EXT means that an mbuf has external storage.

	the code i'm worrying about (m_dup) does not allocate the cluster by
	itself - the cluster was allocated by someone else, so m_dup has
	no idea about how the cluster was allocated.

>However, there are other forms of external mbufs (although support for
>them is rarely used).

	we may need to visit the arena, for 9K packets (GbE).

itojun