Re: any reason alloc_chrdev_region() limits itself to major num of 255?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/22/07, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote:
  given that the current definition of a major device number is a
12-bit value (include/linux/kdev_t.h), is there any reason that
dynamic allocation of major numbers via alloc_chrdev_region() limits
itself based on the value of

include/linux/fs.h:#define CHRDEV_MAJOR_HASH_SIZE       255

  sure, i realize there's no real danger of running out of major
numbers, but i'm just curious.  i'm wondering what other places in the
source tree might have a hard-coded value of 255 for that.

probably historical ?  dev_t wasnt always as large as it is now ...
-mike

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux