From: Mike Waychison <Michael.Waychison@Sun.COM>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: [NFS] RE: [autofs] multiple servers per automount
Date: Tue, 14 Oct 2003 19:12:47 -0400 [thread overview]
Message-ID: <3F8C82EF.2010104@sun.com> (raw)
In-Reply-To: <bmhn7t$odm$1@cesium.transmeta.com>
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
H. Peter Anvin wrote:
> Followup to: <3F8C1BB6.9010202@sun.com>
> By author: Mike Waychison <Michael.Waychison@Sun.COM>
> In newsgroup: linux.dev.kernel
>
>>Here is the quick fix for this in RH 2.1AS kernels:
>>
>>http://www.kernelnewbies.org/kernels/rh21as/SOURCES/linux-2.4.9-moreunnamed.patch
>>
>>It makes unnamed block devices use majors 12, 14, 38, 39, as well as 0.
>>
>>I don't know if anyone is working out a better scheme for
>>get_unnamed_dev in 2.6 yet. It does need to be done though. A simple
>>patch for 2.6 would maybe see the unnamed_dev_in_use bitmap grow to
>>PAGE_SIZE, automatically allowing for 32768 unnamed devices.
>>
>
>
> dev_t enlargement, which solves this without a bunch of auxilliary
> majors, should be in 2.6.
>
> -hpa
The problem still remains in 2.6 that we limit the count to 256. I've
attached a quick patch that I've compiled and tested. I don't know if
there is a better way to handle dynamic assignment of minors (haven't
kept up to date in that realm), but if there is, then we should probably
use it instead.
Mike Waychison
[-- Attachment #2: max_anon.patch --]
[-- Type: text/plain, Size: 881 bytes --]
===== fs/super.c 1.108 vs edited =====
--- 1.108/fs/super.c Wed Oct 1 15:36:45 2003
+++ edited/fs/super.c Tue Oct 14 22:52:12 2003
@@ -528,14 +528,22 @@
* filesystems which don't use real block-devices. -- jrs
*/
-enum {Max_anon = 256};
-static unsigned long unnamed_dev_in_use[Max_anon/(8*sizeof(unsigned long))];
+enum {Max_anon = PAGE_SIZE * 8};
+static void *unnamed_dev_in_use = NULL;
static spinlock_t unnamed_dev_lock = SPIN_LOCK_UNLOCKED;/* protects the above */
int set_anon_super(struct super_block *s, void *data)
{
int dev;
spin_lock(&unnamed_dev_lock);
+
+ if (!unnamed_dev_in_use)
+ unnamed_dev_in_use = (void *)get_zeroed_page(GFP_KERNEL);
+ if (!unnamed_dev_in_use) {
+ spin_unlock(&unnamed_dev_lock);
+ return -ENOMEM;
+ }
+
dev = find_first_zero_bit(unnamed_dev_in_use, Max_anon);
if (dev == Max_anon) {
spin_unlock(&unnamed_dev_lock);
next prev parent reply other threads:[~2003-10-14 23:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 15:16 multiple servers per automount Ogden, Aaron A.
2003-10-13 3:23 ` [NFS] " Ian Kent
2003-10-14 7:05 ` Joseph V Moss
2003-10-14 13:37 ` RE: [autofs] " Ian Kent
2003-10-14 13:37 ` Ian Kent
2003-10-14 15:52 ` [NFS] " Mike Waychison
2003-10-14 15:52 ` [NFS] RE: [autofs] " Mike Waychison
2003-10-14 20:44 ` H. Peter Anvin
2003-10-14 23:12 ` Mike Waychison [this message]
2003-10-15 10:28 ` Ingo Oeser
2003-10-15 16:16 ` Mike Waychison
2003-10-23 13:37 ` Ian Kent
2003-10-23 17:00 ` Mike Waychison
2003-10-23 17:09 ` Tim Hockin
2003-10-24 0:47 ` Ian Kent
2003-10-24 1:42 ` Tim Hockin
2003-10-15 7:22 ` Ian Kent
2003-10-15 7:22 ` [NFS] " Ian Kent
2003-10-15 7:22 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2003-10-15 14:31 [NFS] " Lever, Charles
2003-10-15 14:31 ` Lever, Charles
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=3F8C82EF.2010104@sun.com \
--to=michael.waychison@sun.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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.