> Nonsense hodgepodge. See and/or mesaure the impact. I sent numbers in my
> former email. You also missed non-overcommit must be _optional_ [i.e.
> you wouldn't be forced to use it ;)]. Yes, there are users and
> enterprises who require it and would happily pay the 50-100% extra swap
> space for the same workload and extra reliability.
ok.. the last time OOM came up, the main objection to fully
guaranteed vm was the possible huge overhead.
if someone knows how to do it without a huge overhead, i'd love to
see it and try it out.
> At every time you add/delete users, add/delete special apps, etc.
no.. pam_limits knows about groups, and you can specify limit for
that group, one time.
@user ... ... ...
> Rik's killer is quite fine at _default_. But there will be always
> people who won't like it
exactly... so lets try avoid ever needing it. it is a last resort.
> default, use the /proc/sys/vm/oom_killer interface"? As I said
> before there are also such patch by Chris Swiedler and definitely
> not a huge, complex one.
uhmm.. where?
> And these stupid threads could be forgotten for good and all.
:)
> Szaka
regards,
-- Paul Jakma paul@clubi.ie paul@jakma.org PGP5 key: http://www.clubi.ie/jakma/publickey.txt ------------------------------------------- Fortune: The optimum committee has no members. -- Norman Augustine- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/