site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Jun 16, 2006, at 12:01 PM, Andrew Gallatin wrote: It seems to me that you're going to have to have a flag-day of 10.4 anyway, and that 10.x ( x <=3) drivers are going to stop working because of your kernel changes. Absolutely. The question is simply whether it happens once, or for every major release. I really doubt you'd be touching core structures every major release. Despite that having happened for every major release since 10.0, except where it couldn't because it would break something? Thanks to the glory of pipelining, branch prediction and speculative execution, they're much cheaper than you think, but no, if you were to think about it for a second you would realise that an abstract KPI would be worthless if it worked out that way. = Mike _______________________________________________ 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... No, I was complaining about the KPIs being inflicted on us. I cringe every time I write "m = mbuf_next(m)". Should I cringe at this? Is the kernel linker smart enough to replace these function calls with m = m->m_next at link time, or do these function calls really happen? This email sent to site_archiver@lists.apple.com