From: "H. Peter Anvin" <hpa@zytor.com>
To: David Teigland <teigland@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>,
linux-kernel@vger.kernel.org, rubini@gnudd.com, gregkh@suse.de
Subject: Re: [PATCH 3/3] misc: use a proper range for minor number dynamic allocation
Date: Wed, 16 Dec 2009 09:10:34 -0800 [thread overview]
Message-ID: <4B29148A.70805@zytor.com> (raw)
In-Reply-To: <20091216180155.GA23117@redhat.com>
On 12/16/2009 10:01 AM, David Teigland wrote:
>
> I explained here http://lkml.org/lkml/2009/11/9/379 that the dlm does not
> use as many misc devices as has been implied. It starts with 3, and adds
> one for each *userspace* lockspace. There are very few applications (I
> know of 3) that create userspace lockspaces, and they each create about
> one each.
>
> That said, I still intend to rework the dlm to use a single device for all
> lockspaces.
>
Still seems to make more sense to simply move it to a major and/or a
dynamic allocation. misc devices were always meant to be *one of a
kind* devices, which simply didn't need anything but a single allocation.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-12-16 17:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 0:30 [PATCH 1/3] misc: clear allocation bit in minor bitmap when device register fails Thadeu Lima de Souza Cascardo
2009-11-10 0:30 ` [PATCH 2/3] misc: use bitmap/bitops functions for dynamic minor number allocation Thadeu Lima de Souza Cascardo
2009-11-10 0:30 ` [PATCH 3/3] misc: use a proper range for minor number dynamic allocation Thadeu Lima de Souza Cascardo
2009-11-10 0:34 ` H. Peter Anvin
2009-11-10 10:19 ` Alan Cox
2009-11-10 16:45 ` Thadeu Lima de Souza Cascardo
2009-11-11 23:36 ` Andrew Morton
2009-12-15 22:34 ` Andrew Morton
2009-12-15 22:42 ` H. Peter Anvin
2009-12-15 22:56 ` Greg KH
2009-12-15 23:56 ` Alan Cox
2009-12-16 23:14 ` cascardo
2009-12-16 22:51 ` cascardo
2009-12-15 23:37 ` Alan Cox
2009-12-15 23:41 ` Andrew Morton
2009-12-16 18:01 ` David Teigland
2009-12-16 17:10 ` H. Peter Anvin [this message]
2009-12-16 23:21 ` cascardo
2009-12-16 23:05 ` cascardo
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=4B29148A.70805@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cascardo@holoscopio.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@gnudd.com \
--cc=teigland@redhat.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.