| 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, 19 Feb 2008 23:28:28 +0100 From: Pavel Machek <pavel@....cz> To: Paul Jackson <pj@....com> Cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, marcelo@...ck.org, daniel.spang@...il.com, riel@...hat.com, akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk, linux-fsdevel@...r.kernel.org, a1426z@...ab.com, jonathan@...masters.org, zlynx@....org Subject: Re: [PATCH 0/8][for -mm] mem_notify v6 On Tue 2008-02-19 09:00:08, Paul Jackson wrote: > Kosaki-san wrote: > > Thank you for wonderful interestings comment. > > You're most welcome. The pleasure is all mine. > > > you think kill the process just after swap, right? > > but unfortunately, almost user hope receive notification before swap ;-) > > because avoid swap. > > There is not much my customers HPC jobs can do with notification before > swap. Their jobs either have the main memory they need to perform the > requested calculations with the desired performance, or their job is > useless and should be killed. Unlike the applications you describe, > my customers jobs have no way, once running, to adapt to less > memory. Sounds like a job for memory limits (ulimit?), not for OOM notification, right? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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