The only change is to update things to 2.4.2-pre3: ftp://ftp.kernel.org/pub/linux/kernel/people/davem/zerocopy-2.4.2p3-1.diff.gz All the reports I am getting now appear to be consistent, and they all basically show me that: 1) There are no known bugs (as in things that crash the kernel or corrupt data) 2) The loopback etc. raw performance anomalies have been killed by the P-II Mendocino unaligned memcpy workaround. 3) The acenic/gbit performance anomalies have been cured by reverting the PCI mem_inval tweaks. 4) The zerocopy patches have a small yet non-neglible cpu usage cost for normal write/send/sendmsg. If this truly is the current state of affairs, then I am pretty happy as this is where I wanted things to be when I first began to publish these zerocopy diffs. The next step is to begin profiling things heavily to see if we can back some of that extra cpu usage the pages SKBs afford us. Due to the powder rule (Lake Tahoe received 6 or so feet of snow this past weekend) I will be a bit quiet until Friday night. However, I'll be doing my own profiling of the zerocopy stuff on my laptop while I'm up there. Later, David Snowboard Miller [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/