From: markus reichelt <ml@mareichelt.de>
To: linux-kernel@vger.kernel.org
Subject: Re: max_loop limit
Date: Thu, 22 Mar 2007 12:00:58 +0100 [thread overview]
Message-ID: <20070322110058.GB23664@tatooine.rebelbase.local> (raw)
In-Reply-To: <460236CE.1030303@slax.org>
[-- Attachment #1: Type: text/plain, Size: 334 bytes --]
* Tomas M <tomas@slax.org> wrote:
> I hope you will like it and you will include it in kernel.
> Or, if not, maybe this patch will start some debate regarding
> the current insufficient limit of 255 loop devices.
255 loop devices are insufficient? What kind of scenario do you have
in mind?
--
left blank, right bald
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-22 11:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 7:57 max_loop limit Tomas M
2007-03-22 11:00 ` markus reichelt [this message]
2007-03-22 11:37 ` Tomas M
2007-03-22 13:42 ` Eric Dumazet
2007-03-22 13:42 ` Jens Axboe
2007-03-22 13:52 ` Eric Dumazet
2007-03-22 13:54 ` Jens Axboe
2007-03-22 14:11 ` William Lee Irwin III
2007-03-22 15:22 ` Arjan van de Ven
2007-03-22 16:09 ` Pádraig Brady
2007-03-28 23:34 ` Karel Zak
[not found] ` <20070322151826.c1421851.dada1@cosmosbay.com>
[not found] ` <20070322142306.GU19922@kernel.dk>
[not found] ` <20070322153603.1f5d442d.dada1@cosmosbay.com>
2007-03-22 15:31 ` max_loop limit - paid job offer Tomas M
2007-03-22 14:33 ` max_loop limit Al Viro
2007-03-22 19:51 ` Olivier Galibert
2007-03-22 14:25 ` Tomas M
2007-03-23 1:34 ` Jan Engelhardt
2007-03-23 23:26 ` [PATCH] " Jan Engelhardt
2007-03-25 0:17 ` Ken Chen
2007-03-25 0:29 ` Ken Chen
2007-03-25 8:40 ` Tomas M
2007-03-28 23:41 ` Karel Zak
2007-03-29 3:54 ` Kyle Moffett
2007-03-29 4:16 ` [PATCH] max_loop limit, t2 Jan Engelhardt
2007-03-29 8:38 ` [PATCH] max_loop limit, loop.c final working version Tomas M
2007-03-29 14:16 ` max_loop limit Bill Davidsen
2007-03-22 13:53 devzero
2007-03-22 23:23 devzero
2007-03-23 8:59 ` Tomas M
2007-03-22 23:37 roland
2007-03-29 14:20 ` Bill Davidsen
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=20070322110058.GB23664@tatooine.rebelbase.local \
--to=ml@mareichelt.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 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.