From owner-freebsd-current Sun Jun 14 22:36:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14820 for freebsd-current-outgoing; Sun, 14 Jun 1998 22:36:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14815 for ; Sun, 14 Jun 1998 22:36:49 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id WAA27784; Sun, 14 Jun 1998 22:25:39 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd027782; Mon Jun 15 05:25:35 1998 Date: Sun, 14 Jun 1998 22:25:32 -0700 (PDT) From: Julian Elischer To: Poul-Henning Kamp cc: Brian Somers , current@FreeBSD.ORG Subject: Re: RFC: Change to the device interface In-Reply-To: <3413.897885129@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Jun 1998, Poul-Henning Kamp wrote: > In message , Juli > an Elischer writes: > > > > > >On Mon, 15 Jun 1998, Poul-Henning Kamp wrote: > > > >> In message , Juli > >> > >> Julian, I think this is needless generality. > >> > >> Just add one new entrypoint to the devsw structure "openclose" > >> which receives as argument the number of currently open R/O and > >> R/W opens, as well as the delta which is causing this call, and > >> the credentials of the process affecting the change. > >> > > > >Ok, so you need to keep the opens counted somewhere else.. > >where? In the vnode? > > Wouldn't that be the logical place ? > It would certainly be so if you didn't want to allow the driver itself to associate an IO request with an open() session. SLICE on the other hand has to aggregate these counts so it has to keep track of all this anyhow. so it would be duplicating this It also doesnt take aliased vnodes into account very well. maybe its a better idea to specify what the AIM is first :-) I have a request from Justin that he wants to be associate an open (or mode upgrade) with a user (we can already do that) and an IO request with a particular open and to be aware at any time of how many clients he has. point 1 is normal (struct proc *) point 2 needs something like what I suggest point 3 would be covered by your suggestion. so the question is: what do we want? I personally like th idea of ALWAYS being able to link an io request to some session, even if just for accounting purposes. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message