From owner-freebsd-hackers Thu Dec 18 14:50:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA29719 for hackers-outgoing; Thu, 18 Dec 1997 14:50:31 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA29707 for ; Thu, 18 Dec 1997 14:50:16 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id OAA11174; Thu, 18 Dec 1997 14:50:06 -0800 (PST) Message-ID: <19971218145005.37073@hydrogen.nike.efn.org> Date: Thu, 18 Dec 1997 14:50:05 -0800 From: John-Mark Gurney To: Mike Smith Cc: Darren Reed , freebsd-hackers@FreeBSD.ORG Subject: Re: converting drivers to dynamic memory... References: <19971218065107.10999@hydrogen.nike.efn.org> <199712182230.JAA01661@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199712182230.JAA01661@word.smith.net.au>; from Mike Smith on Fri, Dec 19, 1997 at 09:00:02AM +1030 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Smith scribbled this message on Dec 19: > > yep, I think that would be a great addition... IMO, once devfs has > > finally been completed, we will still need a minor number of the void * > > (I happen to like the name dev_info_t), the minor so that we know what > > part of the device driver we are accessing... else we would need to > > allocate a bunch of small structs like: > > struct { > > int option; > > struct devicedata data; > > } > > > > which would be really wasteful of precious memory resources... > > No. I take your point about wanting to have multiple DEVFS entries > referencing a single softc structure though; you might want to have > something like: > > struct devfs_softc_reference > { > void *softc; > int token; > } > > inside the devfs_node structure. yep, that's what I'd like... > Forget the btree model; it's not going to fly in the face of a direct > reference approach. I will once devfs and the driver interface supports it... but devfs and the interface doesn't even support passing a token yet (well, it does if you call minor number a token)... I just proposed a simple stop gap meassure that would get the ball rolling.. when did I ever say that we should in the long run choose using a btree over the "correct" way to do it?? I only said it would require an interface change (which hasn't even started to happen, sure the devfs code is in place, but actually USING it to pass tokens hasn't even begun), which I stated, I wasn't going to do... but I proposed using the btree method as a stepping stone to get to the final destination... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking P.O. Box 5693, 97405 Live in Peace, destroy Micro$oft, support free software, run FreeBSD