From: Valdis.Kletnieks@vt.edu
To: Bill Davidsen <davidsen@tmr.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Ken Chen <kenchen@google.com>, Tomas M <tomas@slax.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] remove artificial software max_loop limit
Date: Sat, 07 Apr 2007 12:18:52 -0400 [thread overview]
Message-ID: <11158.1175962732@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 06 Apr 2007 16:33:32 EDT." <4616AE9C.9060400@tmr.com>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
On Fri, 06 Apr 2007 16:33:32 EDT, Bill Davidsen said:
> Jan Engelhardt wrote:
> > Who cares if the user specifies max_loop=8 but still is able to open up
> > /dev/loop8, loop9, etc.? max_loop=X basically meant (at least to me)
> > "have at least X" loops ready.
> >
> You have just come up with a really good reason not to do unlimited
> loops.
That, and I'd expect the intuitive name for "have at least N ready" to
be 'min_loop=N'. 'max_loop=N' means (to me, at least) "If I ask for N+1,
something has obviously gone very wrong, so please shoot my process before
it gets worse".
Maybe what's needed is *both* a max_ and min_ parameter?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-04-07 16:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2007-04-07 16:34 ` Bill Davidsen
2007-03-30 21:46 ` Andrew Morton
2007-03-30 21:52 ` Jan Engelhardt
2007-04-01 9:16 devzero
2007-04-01 10:53 devzero
2007-04-01 18:03 ` Ken Chen
2007-04-01 19:00 ` Jeff Dike
2007-04-01 18:36 devzero
2007-04-01 18:43 ` Kyle Moffett
2007-04-01 18:54 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=11158.1175962732@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=davidsen@tmr.com \
--cc=jengelh@linux01.gwdg.de \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas@slax.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®