Skip to contentSkip to conversation

Larger dev_t

DISCUSSION [email protected] 1 participant 1 message Mar 24, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 1 line

Also for 2.5, kdev_t needs to go away, along with all those arrays

Yes, it has been said many times, and I get the impression that many people actually did it.

Maybe everybody with code or at least a detailed setup should demonstrate what was done so that we can compare merits of several approaches.

The stuff I sent earlier today was the dev_t part. The next part I hope to send one of these days is the interface between dev_t and kdev_t.
(Most people think that kdev_t is an integer, I think that it is a pointer. Since dev_t now can be large and arrays cannot be used, we need some hash lookup to find the structure corresponding to the number. And the code is roughly speaking identical to Al's bdev code, only now used both for bdev and cdev.)

(Funny enough Al's code does not solve the only small problem I had six years ago: a mknod with funny numbers does not mean that some such device actually exists. In reality we only want to convert number into device pointer when the device is opened, but the current kernel code does

	init_special_inode(inode, mode, rdev);
for a mknod, and if it was a block device
	inode->i_bdev = bdget(rdev);

so that it does allocate a struct to this nonsense device.)

Andries