> > Once we bite off designing a scalable MP-safe network buffer
> > allocation, the embedded m_ext is simply *not necessary* to acheive
> > either your goals or my goals.
> 
> how can you change mapping state of shared external storage,
> without the small shared header?
> only way i can think of is grabbing the global lock and
> iterate all mbufs which might reference the external storage.

it might be an alternative to share _m_ext in mbuf directly (and
give up supporting MEXTREMOVE).  do you prefer it?

> > (See the FreeBSD-5 apporoach, either
> > source-code or the slightly different slant in Bosko' Milecek's BSDcon
> > paper, for an existence proof)
> > 
> > Thus, the embedded bm_ext idea is *NOT* orthogonal to a well-designed,
> > scalable mbuf-allocation design.
> 
> as i repeatedly said, freebsd5 uses the similar small headers.
> (which is embedded in slab headers for cluster mbufs,
> and malloc'ed in the case of m_extadd.)
> why do you ignore the point, or am i misunderstanding something?

jonathan, can you please answer my this silly question?  thanks.

YAMAMOTO Takashi