From owner-freebsd-usb@FreeBSD.ORG Mon Jan 10 07:07:51 2005 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF8A316A4CE for ; Mon, 10 Jan 2005 07:07:51 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D1EE43D2D for ; Mon, 10 Jan 2005 07:07:51 +0000 (GMT) (envelope-from dinkevich@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so313025rne for ; Sun, 09 Jan 2005 23:07:50 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:x-sender:x-mailer:date:to:subject:cc:in-reply-to:references:mime-version:content-type:from; b=QxrAHwdgXfOgkjT/XSmzzF+osh1eitj41GCmifEWv4skWSKCkb/rQ4U8G8goW2Ral5z8puLat/QGFOkGTV1KRhNOyvAiilACvCtSQ/xdw8W/RVoghlMh8PR3wUJFvmAWwHUL0ED9UpGRiYVPmRCV9LhrWCkxCfPpiG3EOmI9WCU= Received: by 10.38.96.67 with SMTP id t67mr346142rnb; Sun, 09 Jan 2005 23:07:50 -0800 (PST) Received: from becker.Dinkevich.com ([194.90.113.98]) by smtp.gmail.com with ESMTP id 73sm1302581rna.2005.01.09.23.07.48; Sun, 09 Jan 2005 23:07:50 -0800 (PST) Message-Id: <6.1.2.0.2.20050110085622.0338a980@pop.gmail.com> X-Sender: dinkevich@pop.gmail.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Mon, 10 Jan 2005 09:05:46 +0200 To: "M. Warner Losh" In-Reply-To: <20050109.200910.28786915.imp@bsdimp.com> References: <6.1.2.0.2.20050109174427.0802c640@pop3> <20050109.125213.02300240.imp@bsdimp.com> <41E1C8C5.4070605@elischer.org> <20050109.200910.28786915.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; From: Boris Dinkevich cc: freebsd-usb@hub.freebsd.org cc: dinkevich@gmail.com cc: julian@elischer.org Subject: Re: stack synchronization X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 07:07:51 -0000 Hello everyone, I see no reference to giant locking in 5.3 (except in event/task threads) Does this not affect performance when multiple devices are connected to the host ? Also, I have seen a modification to the bsd stack by Hans Petter Selasky, where he uses per bus mtxes for locking, is this not the better approach to the problem ? Interrupt is synced via Giant ? Best Regards Boris Dinkevich At 05:09 AM 10/1/2005, M. Warner Losh wrote: >In message: <41E1C8C5.4070605@elischer.org> > Julian Elischer writes: >: M. Warner Losh wrote: >: > In message: <6.1.2.0.2.20050109174427.0802c640@pop3> >: > Boris Dinkevich writes: >: > : Hello everyone, >: > : >: > : When going over the usb-host stack, it appears that synchronization >is done >: > : via splusb/x. >: > : But in the 5.3 release, these functions are implemented at stubs. >: > : >: > : How is the sync done then ? >: > : >: > : Also, with soft_interrupts, it appears there is no need for spls, am I >: > : correct ? >: > >: > Giant locking. >: > >: > I have patches to move the interrupt outside of giant, but the rest of >: > the stack is still under giant locking. >: >: it may be worth just adding a single "usb system" lock.. > >well duh! However, there's a lot of things that can trivially be done >with giant. Locking with a usb subsystem lock takes a lot more >effort... > >Warner