| 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: Fri, 4 Mar 2011 09:11:32 +0100 From: Daniel Poelzleithner <poelzi@...lzi.org> To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, containers@...ts.linux-foundation.org Subject: Re: cgroup memory, blkio and the lovely swapping On Fri, 4 Mar 2011 16:54:55 +0900 KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote: > Now, blkio cgroup does work only with synchronous I/O(direct I/O) > and never work with swap I/O. And I don't think swap-i/o limit > is a blkio matter. I'm totally unsure about what subsystem it really belongs to. It is memory for sure, but disk access, which it actually affects, belongs to the blkio subsystem. Is there a technical reason why swap I/O is not run through the blkio system ? > Memory cgroup is now developping dirty_ratio for memory cgroup. > By that, you can control the number of pages in writeback, in memory > cgroup. I think it will work for you. I'm not sure that fixes the fairness problem on swapio. Just having a larger buffer before a writeback happens will reduce seeks, but not give fair share of io in swap in. It's good to control over it on cgroup level, but i doubt it will fix the problem. kind regards Daniel -- 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