From owner-freebsd-current@FreeBSD.ORG Fri Sep 2 17:31:52 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A51D16A41F for ; Fri, 2 Sep 2005 17:31:52 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACF4D43D45 for ; Fri, 2 Sep 2005 17:31:51 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from [10.50.40.201] (Not Verified[10.50.40.201]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Fri, 02 Sep 2005 13:47:13 -0400 From: John Baldwin To: current@FreeBSD.org Date: Fri, 2 Sep 2005 13:21:35 -0400 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509021321.36320.jhb@FreeBSD.org> Cc: Subject: Locking for txp(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 17:31:52 -0000 I have a patch that adds locking to txp(4) and marks it MPSAFE. I also think I've found a bug in the driver in low-memory conditions where txp_rxbuf_reclaim() can't allocate a new mbuf cluster, so I'd appreciate it if folks could test this. Thanks. http://www.FreeBSD.org/~jhb/patches/txp_locking.patch -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org