Re: [patch] remove artificial software max_loop limit

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: pgp14HRvHg7pG.pgp
Description: PGP signature

---

• Follow-Ups:
  • Re: [patch] remove artificial software max_loop limit
    • From: Bill Davidsen <[email protected]>

• References:
  • Re: [patch] remove artificial software max_loop limit
    • From: Bill Davidsen <[email protected]>

• Prev by Date: Re: Ten percent test
• Next by Date: SD scheduler testing hitch
• Previous by thread: Re: [patch] remove artificial software max_loop limit
• Next by thread: Re: [patch] remove artificial software max_loop limit
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]