From: Jon Masters <jonmasters@gmail.com>
To: Thomas Habets <thomas@habets.pp.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] oom_pardon, aka don't kill my xlock
Date: Mon, 27 Sep 2004 13:17:22 +0100 [thread overview]
Message-ID: <35fb2e5904092705174e28b671@mail.gmail.com> (raw)
In-Reply-To: <200409271401.03817.thomas@habets.pp.se>
On Mon, 27 Sep 2004 14:00:56 +0200, Thomas Habets <thomas@habets.pp.se> wrote:
> > What we need is a mechanism to have a giant brainstraw emerge from the
> > front casing of the machine and suck the brains out of the guy running
> > a server with overcommit issues.
>
> So the way to deal with OOM-killer issues is to laugh at people who encounter
> it? How very openbsd of you.
Actually I was leaning towards non-overcommit as an approach if you're
that worried (I know user non-overcommit is not a perfect solution). I
like Andrea's patch but this is one of these circular issues that'll
keep popping up from time to time because there isn't a perfect
solution that works for everyone all of the time. I typically find oom
results in things I want dying underneath me. Windows does something
with extending its paging file when this happens - has anyone looked
at weird alternatives such as this for desktop Linux?
> And I don't run X or xlock on any of my servers. IOW: this was not a server.
Yes ok. I was picking at the OOM Killer rather than at you - you just
didn't get my sense of humour but that's ok.
Jon.
next prev parent reply other threads:[~2004-09-27 12:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 12:00 [PATCH] oom_pardon, aka don't kill my xlock Thomas Habets
2004-09-27 12:17 ` Jon Masters [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-22 23:23 Thomas Habets
2004-09-23 0:01 ` Nick Piggin
2004-09-23 0:07 ` William Lee Irwin III
2004-09-23 4:45 ` Tonnerre
2004-09-23 6:57 ` Thomas Habets
2004-09-23 12:24 ` Tonnerre
2004-09-23 13:32 ` Thomas Habets
2004-09-23 23:45 ` Andries Brouwer
2004-09-24 13:19 ` Alan Cox
2004-09-24 19:58 ` Thomas Habets
2004-09-24 21:15 ` Alan Cox
2004-09-25 10:08 ` Thomas Habets
2004-09-27 10:41 ` Marcelo Tosatti
2004-09-27 12:54 ` Lars Marowsky-Bree
2004-09-27 13:12 ` Jon Masters
2004-09-27 12:36 ` Alan Cox
2004-09-27 13:35 ` Marcelo Tosatti
2004-09-27 15:59 ` Jon Masters
2004-09-27 17:12 ` Herbert Poetzl
2004-09-27 16:42 ` Marcelo Tosatti
2004-09-28 13:33 ` Herbert Poetzl
2004-09-28 12:32 ` Marcelo Tosatti
2004-09-28 23:55 ` Herbert Poetzl
2004-09-27 23:07 ` Jon Masters
2004-09-29 0:49 ` Andries Brouwer
2004-09-24 14:07 ` Pavel Machek
2004-09-24 22:57 ` Jon Masters
2004-09-25 16:32 ` Andrea Arcangeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35fb2e5904092705174e28b671@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@habets.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox