From: Jeremy Fitzhardinge <jeremy@goop.org>
To: James Sutherland <jas88@cam.ac.uk>
Cc: jfm2@club-internet.fr, ingo.oeser@informatik.tu-chemnitz.de,
riel@conectiva.com.br, torvalds@transmeta.com,
linux-mm@kvack.org
Subject: Re: Discussion on my OOM killer API
Date: Fri, 27 Oct 2000 21:48:16 -0700 [thread overview]
Message-ID: <20001027214816.C4324@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10010272309040.17292-100000@dax.joh.cam.ac.uk>; from jas88@cam.ac.uk on Fri, Oct 27, 2000 at 11:11:11PM +0100
[-- Attachment #1: Type: text/plain, Size: 245 bytes --]
On Fri, Oct 27, 2000 at 11:11:11PM +0100, James Sutherland wrote:
> Ehm... nope. mlockall().
Better make sure it's statically linked... don't want every random library
locked down in their entirety just because the oom killer is using it.
J
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2000-10-28 4:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001019122331.H840@nightmaster.csn.tu-chemnitz.de>
2000-10-19 17:02 ` Rik van Riel
2000-10-26 20:47 ` Linus Torvalds
2000-10-26 21:16 ` Rik van Riel
2000-10-26 22:33 ` Mark Hahn
2000-10-26 23:58 ` James Sutherland
2000-10-27 0:10 ` Linus Torvalds
2000-10-27 6:46 ` James Sutherland
2000-10-27 7:39 ` Gábor Lénárt
2000-10-27 13:54 ` James Sutherland
2000-10-27 17:10 ` Ingo Oeser
2000-10-27 17:36 ` James Sutherland
2000-10-27 22:12 ` jfm2
2000-10-27 22:11 ` James Sutherland
2000-10-27 22:43 ` jfm2
2000-10-27 22:51 ` James Sutherland
2000-10-28 4:48 ` Jeremy Fitzhardinge [this message]
2000-10-28 7:29 ` James Sutherland
2000-10-30 9:02 ` G?bor L?n?rt
2000-10-30 9:41 ` James Sutherland
2000-10-30 9:53 ` G?bor L?n?rt
2000-10-30 12:18 ` J.A. Sutherland
2000-10-29 19:30 ` Ingo Oeser
2000-10-29 20:41 ` James Sutherland
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=20001027214816.C4324@goop.org \
--to=jeremy@goop.org \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=jas88@cam.ac.uk \
--cc=jfm2@club-internet.fr \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.com \
/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