From owner-freebsd-net@FreeBSD.ORG Mon Dec 31 07:09:01 2007 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C6C516A417 for ; Mon, 31 Dec 2007 07:09:01 +0000 (UTC) (envelope-from tofig@freebsd.az) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by mx1.freebsd.org (Postfix) with ESMTP id 6A00113C43E for ; Mon, 31 Dec 2007 07:09:01 +0000 (UTC) (envelope-from tofig@freebsd.az) Received: by rv-out-0910.google.com with SMTP id l15so4874658rvb.43 for ; Sun, 30 Dec 2007 23:09:00 -0800 (PST) Received: by 10.141.22.1 with SMTP id z1mr245622rvi.277.1199084940444; Sun, 30 Dec 2007 23:09:00 -0800 (PST) Received: by 10.140.142.6 with HTTP; Sun, 30 Dec 2007 23:09:00 -0800 (PST) Message-ID: <342414370712302309i2fbaff2ex4888d51d51eaa99c@mail.gmail.com> Date: Mon, 31 Dec 2007 11:09:00 +0400 From: "Tofig Suleymanov" To: "Robert Watson" In-Reply-To: <20071231002840.N21364@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4777690B.1030403@freebsd.az> <20071230170217.T6382@fledge.watson.org> <47780CE4.3000302@freebsd.az> <20071231002840.N21364@fledge.watson.org> Cc: freebsd-net@freebsd.org Subject: Re: if_start running deferred for Giant 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: Mon, 31 Dec 2007 07:09:01 -0000 On 12/31/07, Robert Watson wrote: > > On Mon, 31 Dec 2007, Tofig Suleymanov wrote: > > >>> xxxxxx kernel: ib0: if_start running deferred for Giant > >>> > >>> I am not sure what does this exactly mean. > >>> > >>> Any help would be appreciated. > >> > >> This occurs when a network device driver has declared itself IFF_NEEDSGIANT > >> -- that is, has declared that it requires the Giant lock in order to > >> operate. As this is considered an undesirable state of affairs for a device > >> driver, a warning is printed. However, in the case of a USB device driver, > >> it is currently required as the USB framework is not MPSAFE, so requires > >> Giant. > > > > Thanks for clarification. Does it mean that I can ignore this notice when > > dealing with USB framework ? > > For now, yes. When, at some point, the USB framework is MPSAFE, we'll need to > remove IFF_NEEDSGIANT, and I'd make sure that your device driver is as ready > as it can be to operate Giant-free once that's done. > > Robert N M Watson > Computer Laboratory > University of Cambridge > Now it is clear to me. Thanks for your help.