| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 22 Mar 2007 14:54:57 +0100 From: Jens Axboe <jens.axboe@...cle.com> To: Eric Dumazet <dada1@...mosbay.com> Cc: Tomas M <tomas@...x.org>, linux-kernel@...r.kernel.org Subject: Re: max_loop limit On Thu, Mar 22 2007, Eric Dumazet wrote: > On Thu, 22 Mar 2007 14:42:31 +0100 > Jens Axboe <jens.axboe@...cle.com> wrote: > > > > > This time, you would be limited to 16384 loop devices on x86_64, 32768 on i386 :) > > > > But this still wastes memory, why not just allocate each loop device > > dynamically when it is set up? The current approach is crap, it is just > > wasting memory for loop devices, queues, etc. > > > > Sure, but it's the first Tomas patch :) The more the reason to guide him in the direction of a right solution, instead of extending the current bad one! > Apparently the 'current crap' didnt caugth someone else attention. I guess most people don't care, 8 is enough for them and the wasted memory isn't too much to care about - 8 devices and only one used, is wasting at least ~14kb on my machine here. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists