public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jose Luis Domingo Lopez <linux-kernel@24x7linux.com>
To: linux-kernel@vger.kernel.org
Cc: roland <for_spam@gmx.de>
Subject: Re: maximum of 256 loop devices - not enough for cdrom server
Date: Thu, 26 May 2005 22:14:38 +0200	[thread overview]
Message-ID: <20050526201438.GA23028@localhost> (raw)
In-Reply-To: <013d01c5618f$2939d240$2000000a@schlepptopp>

[-- Attachment #1: Type: text/plain, Size: 977 bytes --]

On Thursday, 26 May 2005, at 03:06:34 +0200,
roland wrote:

> Is there a possible solution for this "problem" ?
> 
Beware: not a kernel hacker, not even a proficient programmer.

It seems it would be easy, just changing the max current loop device
number value (256) to something higher (i.e., 4096). Note, however, that
loop devices are described by an array of structs statically allocated at
module load time, so expect memory usage to grow linearly and search operations 
on the array become slower at least linearly.

There is one thing that maybe would need some attetion: minor number
allocation for loopback block devices. Now they are assigned at module
initialization, but I don't know the current status in the Linux kernel
with respect to (major,minor) sizes and allocation.

Hope someone more knowledgeable jumps into this :-)

Greetings,

-- 
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Sid (Linux 2.6.11.10)


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-05-26 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26  1:06 maximum of 256 loop devices - not enough for cdrom server roland
2005-05-26 20:14 ` Jose Luis Domingo Lopez [this message]
2005-06-04  1:14   ` randy_dunlap
  -- strict thread matches above, loose matches on Subject: below --
2007-01-25 17:38 devzero

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=20050526201438.GA23028@localhost \
    --to=linux-kernel@24x7linux.com \
    --cc=for_spam@gmx.de \
    --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