site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com -josh On Jun 28, 2005, at 1:16 PM, Carl Smith wrote: Sorry, guess I was expanding on the original question. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com You can't create an ifp from scratch. An ifp is an interface pointer. It points to an interface. The interface is allocated by some driver or the stack in the case of a few built-in virtual interfaces such as lo0. You can't just make one up. Well, you can, but then you'll have lots of other questions. I was trying to get the consensus, is it OK to keep this "copied" 'ifp' around or should I create everything 'new' from scratch, when inputting my data into the mbuf? I am asking this question relating to performance, timing, memory and potential errors. Is there any benefit to creating the 'ifp' from scratch versus keeping a copy around? Carl smime.p7s