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 18:21:32 +0200 [thread overview]
Message-ID: <48BEB98C.8030303@kernel.org> (raw)
In-Reply-To: <48BEB759.4050503@zytor.com>
H. Peter Anvin wrote:
> But just allocating a big bucket of device numbers and throw it all into
> a pot semirandomly is likely to cause more damage, not less.
To use ext devt, the system has to use udev for device numbers. As long
as udev is used, the major number doesn't matter. In addition, breaking
drastically (e.g. can't find the device) seems better than subtle
failure (e.g. weird partition number calculation based on the
traditional minor number scheme) and CONFIG_DEBUG_BLOCK_EXT_DEVT is
exactly aimed at making breakages obvious.
I don't really see there's much to gain by sharing the original major
numbers.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-09-03 16:23 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
2008-09-03 16:12 ` H. Peter Anvin
2008-09-03 16:21 ` Tejun Heo [this message]
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=48BEB98C.8030303@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).