| 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: Wed, 1 Nov 2006 16:09:42 -0800 From: "Paul Menage" <menage@...gle.com> To: "Paul Jackson" <pj@....com> Cc: balbir@...ibm.com, dev@...nvz.org, vatsa@...ibm.com, sekharan@...ibm.com, ckrm-tech@...ts.sourceforge.net, haveblue@...ibm.com, linux-kernel@...r.kernel.org, matthltc@...ibm.com, dipankar@...ibm.com, rohitseth@...gle.com Subject: Re: [ckrm-tech] RFC: Memory Controller On 11/1/06, Paul Jackson <pj@....com> wrote: > > Essentially, if my understanding is correct, zone reclaim has tasks > that are asking for memory first do some work towards keeping enough > memory free, such as doing some work reclaiming slab memory and pushing > swap and pushing dirty buffers to disk. True, it would help with keeping the machine in an alive state. But when one task is allocating memory, it's still going to be pushing out pages with random owners, rather than pushing out its own pages when it hits it memory limit. That can negatively affect the performance of other tasks, which is what we're trying to prevent. You can't just say that the biggest user should get penalised. You might want to use 75% of a machine for an important production server, and have the remaining 25% available for random batch jobs - they shouldn't be able to impact the production server. Paul - 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