Date: Sun, 23 Jun 2002 23:36:28 -0600 From: "Kenneth D. Merry" <ken@kdm.org> To: current@FreeBSD.org Cc: net@FreeBSD.org, gallatin@FreeBSD.org, wpaul@FreeBSD.org, bmilekic@FreeBSD.org, alc@FreeBSD.org Subject: zero copy code checkin in 2 days, new snapshot Message-ID: <20020623233627.A44237@panzer.kdm.org>
next in thread | raw e-mail | index | archive | help
I'm planning on checking in the zero copy sockets code Tuesday evening, MDT. If there are any concerns, I'm more than willing to delay it. I've also released a new snapshot, based on -current from June 23rd, 2002: http://people.freebsd.org/~ken/zero_copy/ The following changes went into this snapshot: - Added a zero_copy(9) man page that describes the general characteristics of the zero copy send and receive code, and what an application author should do to take advantage of the code. - Update the ti(4) man page to include information on the ioctl interface and the TI_JUMBO_HDRSPLIT and TI_PRIVATE_JUMBOS kernel options. - Added information to NOTES about the ZERO_COPY_SOCKETS, TI_PRIVATE_JUMBOS, TI_JUMBO_HDRSPLIT, MSIZE and MCLSHIFT kernel config options. - ti(4) driver cleanup: cleaned up some unused code, commented out some stray diagnostic printfs, and added a problem describing the transmit flow control problem for posterity. - Added a new jumbo(9) man page that describes the jumbo allocator. I haven't run this through the usual array of regression tests just yet, but that will be done before checkin. (I used the time to run through a buildworld and a LINT build instead.) Feedback and comments are welcome. Again, if there are any concerns, I'm more than willing to delay the checkin. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020623233627.A44237>