From: ebiederm@xmission.com (Eric W. Biederman)
To: Raul Miller <moth@magenta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: guarantee_memory() syscall?
Date: 29 Oct 2000 06:31:45 -0700 [thread overview]
Message-ID: <m1n1fn7ozi.fsf@frodo.biederman.org> (raw)
In-Reply-To: <972824256.eb26eb5e@magenta.com>
In-Reply-To: Raul Miller's message of "Sun, 29 Oct 2000 08:03:35 -0500"
Raul Miller <moth@magenta.com> writes:
> Can anyone tell me about the viability of a guarantee_memory() syscall?
>
> [I'm thinking: it would either kill the process, or allocate all virtual
> memory needed for its shared libraries, buffers, allocated memory, etc.
> Furthermore, it would render this process immune to the OOM killer,
> unless it allocated further memory.]
Except for the OOM killer semantics mlockall already exists.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-29 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-29 13:03 guarantee_memory() syscall? Raul Miller
2000-10-29 13:31 ` Eric W. Biederman [this message]
2000-10-29 18:34 ` James Sutherland
2000-10-29 14:56 ` 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=m1n1fn7ozi.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moth@magenta.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