Date: Mon, 13 Jun 2005 20:59:17 +0100 From: Christoph Hellwig <hch@infradead.org> To: Julian Elischer <julian@elischer.org> Cc: Daniel Eischen <deischen@freebsd.org>, Scott Long <scottl@samsco.org>, Apache Xie <apachexm@hotmail.com>, freebsd-hackers@freebsd.org Subject: Re: contigmalloc() and mmap() Message-ID: <20050613195917.GA5710@infradead.org> In-Reply-To: <42ADE480.9040908@elischer.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> <42ADE480.9040908@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 13, 2005 at 12:54:40PM -0700, Julian Elischer wrote: > though, some people use it for that purpose (e.g. in the original posting). driver writers do all kinds of odd things ;-) > 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). disk drivers use a completely different set of entry points in Linux, and don't have access to per-fd data even in the case they're opened from userland. Character drivers to which this applies OTOH always get a valid struct file, it's guranteed as part of the driver API.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050613195917.GA5710>