From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Overcommit_memory logic fails when swap is off
Date: Mon, 11 Apr 2005 16:27:18 +0100 [thread overview]
Message-ID: <1113233235.9885.40.camel@localhost.localdomain> (raw)
In-Reply-To: <42525107.6060807@egholm-nielsen.dk>
On Maw, 2005-04-05 at 09:49, Martin Egholm Nielsen wrote:
> As I can see, the patch never made it in 2.4.x, right?!
> So, I would like a diff - if still possible :-)
I submitted it ages ago but it was rejected and punted to 2.6. The 2.4
support is available in Red Hat Enterprise Linux 3, so you can pull it
out of the source rpms on the ftp site or out of Centos etc
Alan
next prev parent reply other threads:[~2005-04-11 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 8:49 Overcommit_memory logic fails when swap is off Martin Egholm Nielsen
2005-04-11 15:27 ` Alan Cox [this message]
2005-04-11 18:58 ` Martin Egholm Nielsen
[not found] <3D63C9DE.7479D2E9@icase.edu>
2002-08-21 17:23 ` Alan Cox
2002-08-21 18:04 ` Robert Love
2002-08-21 18:53 ` Alan Cox
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=1113233235.9885.40.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@egholm-nielsen.dk \
/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