From owner-freebsd-net Sun Jun 23 22:36:37 2002 Delivered-To: freebsd-net@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7922237B401; Sun, 23 Jun 2002 22:36:29 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g5O5aSp44275; Sun, 23 Jun 2002 23:36:28 -0600 (MDT) (envelope-from ken) Date: Sun, 23 Jun 2002 23:36:28 -0600 From: "Kenneth D. Merry" 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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-net" in the body of the message