From: Jan Kasprzak <kas@informatics.muni.cz>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: drivers/block/loop.c:max_loop
Date: Mon, 16 Apr 2001 20:00:12 +0200 [thread overview]
Message-ID: <20010416200012.H6934@informatics.muni.cz> (raw)
In-Reply-To: <20010416173942.G6934@informatics.muni.cz> <20010416183637.G9539@suse.de>
In-Reply-To: <20010416183637.G9539@suse.de>; from axboe@suse.de on Mon, Apr 16, 2001 at 06:36:37PM +0200
Jens Axboe wrote:
: On Mon, Apr 16 2001, Jan Kasprzak wrote:
: > Hello,
: >
: > I run a relatively large FTP server, and I've just reached
: > the max_loop limit of loop devices here (I use loopback mount of ISO 9660
: > images of Linux distros here). Is there any reason for keeping
: > the max_loop variable in loop.c set to 8?
:
: Memory requirements -- nothing prevents you from loading it with a
: bigger max count though...
:
I would suggest to make the limit configurable by /proc or
ioctl() in run-time. Or even better, to make all allocations on
first /dev/loopN open. Should I try to implement something like that?
-Yenya
--
\ Jan "Yenya" Kasprzak <kas at fi.muni.cz> http://www.fi.muni.cz/~kas/
\\ PGP: finger kas at aisa.fi.muni.cz 0D99A7FB206605D7 8B35FCDE05B18A5E //
\\\ Czech Linux Homepage: http://www.linux.cz/ ///
Mantra: "everything is a stream of bytes". Repeat until enlightened. --Linus
next prev parent reply other threads:[~2001-04-16 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 15:39 drivers/block/loop.c:max_loop Jan Kasprzak
2001-04-16 16:36 ` drivers/block/loop.c:max_loop Jens Axboe
2001-04-16 18:00 ` Jan Kasprzak [this message]
2001-04-16 18:44 ` drivers/block/loop.c:max_loop Jens Axboe
2001-04-16 18:50 ` drivers/block/loop.c:max_loop 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=20010416200012.H6934@informatics.muni.cz \
--to=kas@informatics.muni.cz \
--cc=axboe@suse.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
all inboxes | Powered by JetHome®