Richard Gooch wrote:
> Do you really need to track devices using inode numbers? Why not use
> the info pointer to <devfs_register>, which will be written to
> file->private_data upon open of the device. You can encode a 32 bit
> number here, or have a pointer to a device instance structure.
> IMO this is far neater than using device/inode numbers.
No, I don't necessarily need inode numbers. So your suggestion
would work. The critical case however is the unregister operation,
where I need to do something close to a revoke operation, and therefore
I need to iterate over all file descriptors that have the file open. The
way I read
your code, it's not possible currently with devfs.
Because my requirements seem quite special, I'm not very convinced
that it does make sense to make devfs more complicated, usbdevfs
is a rather self contained thing right now.
Tom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Mar 06 2000 - 11:34:27 EST