From: H. Peter Anvin <hpa@zytor.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH] misc: use a proper range for minor number dynamic allocation
Date: Mon, 09 Nov 2009 13:32:20 -0800 [thread overview]
Message-ID: <4AF88A64.7010903@zytor.com> (raw)
In-Reply-To: <20091109132836.6cf7f559.akpm@linux-foundation.org>
On 11/09/2009 01:28 PM, Andrew Morton wrote:
>
>> The proposed solution uses the not yet reserved range from 64 to 127. If
>> more devices are needed, we may push 64 to 16. Moreover, if we don't
>> need to give priority to the higher numbers anymore, we can start using
>> the bitmap/bitops functions.
>
> So... misc minors 64 to 127 are presently unused?
>
Perhaps we should just start at 256 and go upward, or even 1048575 and
go downward.
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>,
linux-kernel@vger.kernel.org, device@lanana.org,
rubini@vision.unipv.it, gregkh@suse.de, cluster-devel@redhat.com
Subject: Re: [PATCH] misc: use a proper range for minor number dynamic allocation
Date: Mon, 09 Nov 2009 13:32:20 -0800 [thread overview]
Message-ID: <4AF88A64.7010903@zytor.com> (raw)
In-Reply-To: <20091109132836.6cf7f559.akpm@linux-foundation.org>
On 11/09/2009 01:28 PM, Andrew Morton wrote:
>
>> The proposed solution uses the not yet reserved range from 64 to 127. If
>> more devices are needed, we may push 64 to 16. Moreover, if we don't
>> need to give priority to the higher numbers anymore, we can start using
>> the bitmap/bitops functions.
>
> So... misc minors 64 to 127 are presently unused?
>
Perhaps we should just start at 256 and go upward, or even 1048575 and
go downward.
-hpa
next prev parent reply other threads:[~2009-11-09 21:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 23:28 [PATCH] misc: use a proper range for minor number dynamic allocation Thadeu Lima de Souza Cascardo
2009-11-03 12:05 ` Alessandro Rubini
2009-11-09 21:28 ` [Cluster-devel] " Andrew Morton
2009-11-09 21:28 ` Andrew Morton
2009-11-09 21:32 ` H. Peter Anvin [this message]
2009-11-09 21:32 ` H. Peter Anvin
2009-11-09 22:02 ` Thadeu Lima de Souza Cascardo
2009-11-09 23:29 ` Thadeu Lima de Souza Cascardo
2009-11-09 23:40 ` [Cluster-devel] " Andrew Morton
2009-11-09 23:40 ` Andrew Morton
2009-11-10 11:09 ` [Cluster-devel] " Alan Cox
2009-11-10 11:09 ` Alan Cox
2009-11-10 17:15 ` Thadeu Lima de Souza Cascardo
2009-11-09 23:03 ` [Cluster-devel] " David Teigland
2009-11-09 23:03 ` David Teigland
2009-11-10 11:10 ` Steven Whitehouse
2009-11-10 11:10 ` Steven Whitehouse
2009-11-10 11:16 ` Alan Cox
2009-11-10 11:16 ` Alan Cox
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=4AF88A64.7010903@zytor.com \
--to=hpa@zytor.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.