From owner-freebsd-net Thu Jun 20 22:44:41 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 EE02B37B409; Thu, 20 Jun 2002 22:44:36 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g5L5iar18208; Thu, 20 Jun 2002 23:44:36 -0600 (MDT) (envelope-from ken) Date: Thu, 20 Jun 2002 23:44:35 -0600 From: "Kenneth D. Merry" To: current@FreeBSD.org Cc: net@FreeBSD.org Subject: updated zero copy sockets snapshot available Message-ID: <20020620234435.A18183@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've released a new zero copy sockets snapshot, based on -current from June 20th, 2002. http://people.FreeBSD.org/~ken/zero_copy This fixes the following issues: - Use SLIST_FIRST() macros to access the first entry in a SLIST in uipc_jumbo.c. I didn't fix all of these when Alfred pointed out the problem. (Pointed out by Bosko Milekic.) - Remove superfluous TI_LOCK()/TI_UNLOCK() calls in the zero copy version of ti_newbuf_jumbo(). We already have the lock in all the places ti_newbuf_jumbo() is called. (Prompted by Bosko Milekic.) - In the SIOCGIFMEDIA ioctl in ifmedia_ioctl(), avoid calling malloc() with M_WAITOK. Return an error if the M_NOWAIT malloc fails. The ti(4) driver and the wi(4) driver, at least, call this with a mutex held. This causes witness warnings for 'ifconfig -a' with a wi(4) or ti(4) board in the system. (I've only verified for ti(4)). Feedback and comments are welcome! Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message