From owner-freebsd-net@FreeBSD.ORG Tue May 15 07:21:03 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 29D6116A400 for ; Tue, 15 May 2007 07:21:03 +0000 (UTC) (envelope-from sivakumar.subramani@wipro.com) Received: from wip-ectls-mx1.wipro.com (wip-ectls-mx1.wipro.com [203.91.193.21]) by mx1.freebsd.org (Postfix) with ESMTP id 3F6B113C447 for ; Tue, 15 May 2007 07:21:02 +0000 (UTC) (envelope-from sivakumar.subramani@wipro.com) Received: from wip-ectls-mx1.wipro.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 0A5E7220442 for ; Tue, 15 May 2007 12:22:21 +0530 (IST) Received: from blr-ec-bh02.wipro.com (blr-ec-bh02.wipro.com [10.201.50.92]) by wip-ectls-mx1.wipro.com (Postfix) with ESMTP id F15B222042B for ; Tue, 15 May 2007 12:22:20 +0530 (IST) Received: from blr-m3-msg.wipro.com ([10.114.50.99]) by blr-ec-bh02.wipro.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 15 May 2007 12:22:02 +0530 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 15 May 2007 12:22:08 +0530 Message-ID: <821C7AD2A9F78942B8605979226257739CFBF5@blr-m3-msg.wipro.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IXGB networl driver and locking Thread-Index: AceWvY4ao9PziVGDQDOF30VEGWZQLQ== From: To: X-OriginalArrivalTime: 15 May 2007 06:52:02.0305 (UTC) FILETIME=[8AAEDF10:01C796BD] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: IXGB networl driver and locking X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 May 2007 07:21:03 -0000 Hi all, =20 Same lock is being used in ixgb_intr and ixgb_start. If we get Receive interrupt while processing Xmit (ixgb_start), Will the calling of ixgb_intr() handler be delayed as we will not be getting lock in ixgb_intr since it is already locked in ixgb_start. If it is the case, are we making it as Half duplex, I mean we are allowing either of one Tx (or) Rx. Please clarify. =20 488 ixgb_start (struct ifnet *ifp ) 489 { 490 struct adapter *adapter =3D ifp ->if_softc; 491 =20 492 IXGB_LOCK (adapter ); 493 ixgb_start_locked (ifp ); 494 IXGB_UNLOCK (adapter ); 495 return; 496 } =20 =20 static void 795 ixgb_intr (void *arg ) 796 { ............. ............ IXGB_LOCK (adapter ); ..................... IXGB_UNLOCK (adapter ); =20 Thanks, ~Siva The information contained in this electronic message and any attachments to= this message are intended for the exclusive use of the addressee(s) and= may contain proprietary, confidential or privileged information. If you= are not the intended recipient, you should not disseminate, distribute or= copy this e-mail. Please notify the sender immediately and destroy all= copies of this message and any attachments.=20 WARNING: Computer viruses can be transmitted via email. The recipient= should check this email and any attachments for the presence of viruses.= The company accepts no liability for any damage caused by any virus= transmitted by this email. =20 www.wipro.com