From owner-freebsd-net@FreeBSD.ORG Mon Oct 15 16:58:30 2012 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 895EE87F; Mon, 15 Oct 2012 16:58:30 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id F31658FC08; Mon, 15 Oct 2012 16:58:29 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id q9FGwS3d020954; Mon, 15 Oct 2012 20:58:28 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id q9FGwSTn020953; Mon, 15 Oct 2012 20:58:28 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 15 Oct 2012 20:58:28 +0400 From: Gleb Smirnoff To: Jack Vogel Subject: Re: ixgbe & if_igb RX ring locking Message-ID: <20121015165828.GX89655@glebius.int.ru> References: <5079A9A1.4070403@FreeBSD.org> <20121015162926.GV89655@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "Alexander V. Chernikov" , net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2012 16:58:30 -0000 On Mon, Oct 15, 2012 at 09:39:24AM -0700, Jack Vogel wrote: J> > To me this unlock/lock looks like a legacy from times, when the driver J> > had a single mutex for both TX and RX parts. J> > J> > And removing this re-locking in foo_rxeof() was one of the aims for J> > separate J> > TX/RX locking. J> > J> > Really, lurking through history shows that once driver had split its J> > locking J> > to separate RX and TX part, these unlock/lock was removed. However, later J> > this unlock/lock was added back: J> > J> > J> > http://svnweb.freebsd.org/base/head/sys/dev/e1000/if_igb.c?revision=209068&view=markup J> > J> > , without any comments for the reason it is added back. J> > J> > I did not want to add it back, there were problems that constrained me to J> do so, although its J> been some time, I'd be happy to do some testing again without and see. Can you please dig through mail archives to identify these problems? I can't imagine any. -- Totus tuus, Glebius.