From owner-freebsd-embedded@FreeBSD.ORG Mon Dec 19 06:56:23 2011 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8D64106564A; Mon, 19 Dec 2011 06:56:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 574C78FC08; Mon, 19 Dec 2011 06:56:23 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so6562606vbb.13 for ; Sun, 18 Dec 2011 22:56:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0S/Poq/nqvu/9cXW+c2nl2L9Rm9BEfNd/7/AbjgyxhM=; b=Pu1/asW2mET3thosdsNBH8KOH6FwiKg66FCG7FnMNw+glIFz1WdHA6u9+NQvyd69bk hzZUuYx6jUkb9ap9fVkWSksv1JnXZjGpNev/S652wEopJxMq+Vhz+dmpj266+puVLm6k /CiSn61gyTf0XHZLai0+bmLwi5kgIyt3sP4Qk= MIME-Version: 1.0 Received: by 10.52.90.80 with SMTP id bu16mr10456206vdb.113.1324277782737; Sun, 18 Dec 2011 22:56:22 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.26.50 with HTTP; Sun, 18 Dec 2011 22:56:22 -0800 (PST) In-Reply-To: <2CBD8651-E132-49DC-A082-37A8F5C626EA@bsdimp.com> References: <0F6CC18F-6973-42A2-AC03-F01BF59458AE@lassitu.de> <1100F70E-9DA9-4163-AC9A-423ECE5AA9A3@lassitu.de> <18CABB46-9B9A-41CB-8742-6723C5FF4D67@lassitu.de> <2CBD8651-E132-49DC-A082-37A8F5C626EA@bsdimp.com> Date: Sun, 18 Dec 2011 22:56:22 -0800 X-Google-Sender-Auth: 9F-Jiv5pCLjp7keAHojSTst-M4w Message-ID: From: Adrian Chadd To: Warner Losh Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Oleksandr Tymoshenko , "freebsd-embedded@freebsd.org" Subject: Re: Updated switch/glue patch? X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 06:56:23 -0000 On 18 December 2011 22:42, Warner Losh wrote: >> It's still ridiculously CPU intensive. :( It turns out trying to do >> those locks three times one each GPIO IO line fiddle is a bit over the >> top. > > That's the real problem. =A0WITNESS is a known pigdog on low-end systems,= so measurements with it tend to skew the results a tad too much. =A0On the= other hand, it did magnify the problem to the point it was fixed :) > > The insane locking should be fixed. Yeah. I've done it in my local branch. Hopefully Stefan/I can thrash this out a bit more and get it into the tree soon. I wonder if I can fix up witness a little more. I already found some insane string operations in the witness debugging code, which I've since fixed. Adrian