linux-kernel - RE: System hang problem.

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <200610041724.12514.a1426z@gawab.com>
Date:	Wed, 4 Oct 2006 17:24:12 +0300
From:	Al Boldi <a1426z@...ab.com>
To:	linux-kernel@...r.kernel.org
Subject: RE: System hang problem.

Manish Neema wrote:
> > What you can often do, if you have one application using much memory,
> > is limiting *this application's* memory usage with ulimit. If the
> > application correctly handles malloc()==NULL, then at least your
> > system will behave stably.
>
> The problem is its different application, different user each time (a
> typical large R&D environment). /etc/security/limits.conf allows to set
> max resident set size. Is there a way to limit based on the total
> virtual size?

You mean like: ulimit -v [total VMsize/runqueue]

I suppose, that this could easily be dynamically calculated by the kernel, 
for a tremendously inhibiting OOM-killer effect.


Thanks!

--
Al

-
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/