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: Tue, 10 Mar 2009 15:12:07 -0700 From: Paul Menage <menage@...gle.com> To: Christoph Lameter <cl@...ux-foundation.org> Cc: David Rientjes <rientjes@...gle.com>, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, Andrew Morton <akpm@...ux-foundation.org>, Pekka Enberg <penberg@...helsinki.fi>, Matt Mackall <mpm@...enic.com>, Randy Dunlap <randy.dunlap@...cle.com>, linux-kernel@...r.kernel.org Subject: Re: [patch -mm] cpusets: add memory_slab_hardwall flag On Tue, Mar 10, 2009 at 1:50 PM, Christoph Lameter <cl@...ux-foundation.org> wrote: > > So no real workload just some isolation idea. We definitely have real workloads where a job is allocating lots of slab memory (e.g. network socket buffers, dentry/inode objects, etc) and we want to be able to account the memory usage to each job rather than having all the slab scattered around unidentifiably, and to reduce fragmentation (so when a job finishes, all its sockets close and all its files are deleted, there's a better chance that we'll be able to reclaim some slab memory). We could probably turn those into more synthetic benchmarkable loads if necessary for demonstration. 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