lkml.org 
[lkml]   [2007]   [Apr]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] remove artificial software max_loop limit

On Apr 1 2007 11:10, Ken Chen wrote:
> On 4/1/07, Tomas M <tomas@slax.org> wrote:
>
>> I believe that IF you _really_ need to preserve the max_loop module
>> parameter, then the parameter should _not_ be ignored, rather it
>> should have the same function like before - to limit the loop driver
>> so if you use max_loop=10 for example, it should not allow loop.c to
>> create more than 10 loops.
>
> 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?

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.


Jan
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-04-01 21:11    [W:0.082 / U:0.340 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site