> > One question I've long had on this code is why we use copymsg() rather
 > > than dupmsg().
 > 
 > I _think_ the original rationale was that, since we're just going to
 > do a copymsg() in ip_input->ip_fix_dbref anyway, we might as well skip
 > the wasteful allocation/free of an mblk_t (merely to tell IP, "here;
 > you do the copy") and skip right to the data copy that's going to
 > happen anyway.

Though ip_fix_dbref() is new with Xen, and that copymsg() code has been
there since GLDv3 integrated.

-- 
meem
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to