Garrett D'Amore writes: > > - negotiate with the owners of the interface (start with > > networking-discuss) to have the stability level raised, perhaps > > making it part of the DDI, so that you can use it without trouble; > > or
As noted above, networking-discuss is a better place to discuss the fate of the IP checksum routines. > Actually, it sounds like this particular kind of functionality is useful > enough that it should be part of the DDI. Probably so. In the past, I think the disagreement about this has come from folks who believe in hardware offload and zero-copy performance hooks and need various means to make those things work. > There are functions like this > (for example CRC functionality required for calculating hashes used in > many ethernet MAC chips, SHA1 that is used in various places, etc.) that > should really be part of a common DDI. CRC-32 is already Consolidation Private (see <sys/crc32.h>) and needn't be replicated in drivers. Raising its stability looks fairly straightforward to me. SHA1 is in the kernel crypto framework, along with a bunch of other things. You should check out security-discuss to find those people. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
