linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: device@lanana.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: regarding major number of block extended devt
Date: Wed, 03 Sep 2008 06:13:15 +0200	[thread overview]
Message-ID: <48BE0EDB.20107@kernel.org> (raw)
In-Reply-To: <48BD9F36.8000704@zytor.com>

H. Peter Anvin wrote:
>>  259 block    Block extended device numbers
>>
>>         This is pool of dynamically allocated block device
>>         numbers.  Currently, ide and sd overflows into this
>>         region if there are more partitions than the existing
>>         device number scheme can accomodate, but any block
>>         device can use it and it's not restricted to
>>         overflows.
>>
> 
> It would seem better to simply use the high minors on the
> already-existing ide and scsi majors?

I thought it would be better to break from those majors to make it clear
that the traditional minor allocation scheme isn't followed anymore.
Programs which expect certain majors are likely to need update for how
it deals with minors, so....

Thanks.

-- 
tejun

  reply	other threads:[~2008-09-03  4:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02 12:26 regarding major number of block extended devt Tejun Heo
2008-09-02 12:35 ` Tejun Heo
2008-09-02 20:16   ` H. Peter Anvin
2008-09-03  4:13     ` Tejun Heo [this message]
2008-09-03 16:12       ` H. Peter Anvin
2008-09-03 16:21         ` Tejun Heo
2008-09-03 16:27           ` H. Peter Anvin
2008-09-03 16:45             ` Tejun Heo
2008-09-03 16:57               ` H. Peter Anvin
2008-09-03 18:11               ` H. Peter Anvin
2008-09-04  0:25                 ` Tejun Heo
2008-09-04  0:28                   ` H. Peter Anvin
2008-09-04  0:35                     ` Tejun Heo
2008-09-04  0:43                       ` H. Peter Anvin
2008-09-04 11:50                   ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48BE0EDB.20107@kernel.org \
    --to=tj@kernel.org \
    --cc=device@lanana.org \
    --cc=hpa@zytor.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).