Date: Mon, 13 Jun 2005 12:54:40 -0700 From: Julian Elischer <julian@elischer.org> To: Christoph Hellwig <hch@infradead.org> Cc: Daniel Eischen <deischen@freebsd.org>, freebsd-hackers@freebsd.org, Scott Long <scottl@samsco.org>, Apache Xie <apachexm@hotmail.com> Subject: Re: contigmalloc() and mmap() Message-ID: <42ADE480.9040908@elischer.org> In-Reply-To: <20050613190224.GA4308@infradead.org> References: <Pine.GSO.4.43.0506131332380.23852-100000@sea.ntplx.net> <42ADC762.6010801@elischer.org> <20050613181435.GA3096@infradead.org> <42ADD253.4020606@samsco.org> <20050613184551.GA3853@infradead.org> <42ADD6AC.3060505@samsco.org> <20050613190224.GA4308@infradead.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Christoph Hellwig wrote: >On Mon, Jun 13, 2005 at 12:55:40PM -0600, Scott Long wrote: > > >>>Lot's of driver use file->private to get at per-device data easily, >>>but that's just a shortcut. >>> >>> >>Ok, I thought that you were talking about per-process data being in the >>file descriptor. >> >> > >No, Linux has absolutely no concept of per-process data in driver, and >if you think of it that would be rather bogus anyway (e.g. a driver opening >the same device multiple times) > > though, some people use it for that purpose (e.g. in the original posting). it might not be such a bad idea.. I don't see why the device entrypoints shouldn't have that argument available.. (file descriptor by which we are getting here) As long as it can take account of the fact that not all accesses come via an FD (e.g mounted disks).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42ADE480.9040908>