From: devzero@web.de
To: Ken Chen <kenchen@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] remove artificial software max_loop limit
Date: Sun, 01 Apr 2007 20:36:11 +0200 [thread overview]
Message-ID: <1714123823@web.de> (raw)
>Blame on the dual meaning of max_loop that it uses currently: to
>initialize a set of loop devices and as a side effect, it also sets
>the upper limit. People are complaining about the former constrain,
>isn't it? Does anyone uses the 2nd meaning of upper limit?
>
>- Ken
what sense would it make to set an upper limit at all?
we`re so happy to have none anymore :)
i think andrew`s suggestion is just good:
>So if we're worried about not breaking existing setups, we should retain
>this module parameter as a do-nothing thing, maybe with a
>this-is-going-away warning printk, too.
roland
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
next reply other threads:[~2007-04-01 18:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 18:36 devzero [this message]
2007-04-01 18:43 ` [patch] remove artificial software max_loop limit Kyle Moffett
-- strict thread matches above, loose matches on Subject: below --
2007-04-01 18:54 devzero
2007-04-01 10:53 devzero
2007-04-01 18:03 ` Ken Chen
2007-04-01 19:00 ` Jeff Dike
2007-04-01 9:16 devzero
2007-03-30 7:53 Ken Chen
2007-03-30 8:48 ` Ken Chen
2007-03-30 9:07 ` Jan Engelhardt
2007-03-30 9:25 ` Ken Chen
2007-03-30 16:16 ` Jan Engelhardt
2007-03-30 21:15 ` Andrew Morton
2007-03-30 22:06 ` Ken Chen
2007-03-30 22:50 ` Andrew Morton
2007-03-31 17:07 ` Greg KH
2007-03-31 17:41 ` Andrew Morton
2007-04-01 4:16 ` Ken Chen
2007-04-04 10:31 ` Tomas M
2007-04-04 18:47 ` Andrew Morton
2007-04-01 16:53 ` Tomas M
2007-04-01 16:57 ` Tomas M
2007-04-01 18:10 ` Ken Chen
2007-04-01 19:06 ` Jan Engelhardt
2007-04-06 20:33 ` Bill Davidsen
2007-04-07 16:18 ` Valdis.Kletnieks
2007-04-07 16:34 ` Bill Davidsen
2007-03-30 21:46 ` Andrew Morton
2007-03-30 21:52 ` Jan Engelhardt
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=1714123823@web.de \
--to=devzero@web.de \
--cc=kenchen@google.com \
--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.