From owner-freebsd-bugs@FreeBSD.ORG Fri Jun 24 17:30:21 2011 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 396DA1065689 for ; Fri, 24 Jun 2011 17:30:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 2A1A88FC0C for ; Fri, 24 Jun 2011 17:30:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p5OHULew040754 for ; Fri, 24 Jun 2011 17:30:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p5OHUKcZ040747; Fri, 24 Jun 2011 17:30:20 GMT (envelope-from gnats) Date: Fri, 24 Jun 2011 17:30:20 GMT Message-Id: <201106241730.p5OHUKcZ040747@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Warner Losh Cc: Subject: Re: misc/157903: automated kldload for USB class devices X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Warner Losh List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jun 2011 17:30:21 -0000 The following reply was made to PR conf/157903; it has been noted by GNATS. From: Warner Losh To: Hans Petter Selasky Cc: Robert Millan , freebsd-hackers@FreeBSD.org, freebsd-bugs@FreeBSD.org, FreeBSD-gnats-submit@FreeBSD.org, freebsd-usb@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: misc/157903: automated kldload for USB class devices Date: Fri, 24 Jun 2011 11:21:05 -0600 On Jun 24, 2011, at 7:11 AM, Hans Petter Selasky wrote: > On Friday 24 June 2011 14:59:37 Robert Millan wrote: >> 2011/6/24 Hans Petter Selasky : >>>> Very nice. But why not use variable names instead of hardcoding >>>> numbers? It makes the output much easier to understand. >>>=20 >>> To save memory. >>=20 >> I haven't inspected devd code, but I was under the assumption that >> variables only lived untill resolved. What would be the point of = keeping >> them in memory after devd has finished parsing the config files? >=20 > Hi, >=20 > I haven't checked that, though if you want the readable version, then = you need=20 > to check the source code. >=20 > However I could add some code to print a vendor ID comment, based on = usbdevs. devd keeps them in memory and expands them when the commands are = executed. It will use more memory and be slower if you have lots of = variables. Now much more memory and how much slower? I kinda doubt = you'd notice on modern gear. Warner