Skip to contentSkip to conversation

remove artificial software max_loop limit

PATCH [email protected] 2 participants 2 messages Apr 1, 2007

lore
Share & tools
lore
#0 lore raw
Quoted 6 lines

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:

Quoted 3 lines

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

#1 lore raw
Quoted 10 lines · On Apr 01, 2007, at 14:36:11, [email protected] wrote:
Quoted 6 lines

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 :)

Well, the point of an upper limit might be to keep loop devices from chewing up too much memory on a system. IE: To fail allocating more loopdevs before you run OOM and start killing random userspace processes.

Cheers,
Kyle Moffett