From: Tim Walberg <twalberg@mindspring.com>
To: Christopher Friesen <cfriesen@nortelnetworks.com>
Cc: Brian Gerst <bgerst@didntduck.org>,
Cyrille Beraud <cyrille.beraud@savoirfairelinux.com>,
linux-kernel@vger.kernel.org
Subject: Re: Removing an executable while it runs
Date: Wed, 5 Dec 2001 14:54:42 -0600 [thread overview]
Message-ID: <20011205145442.A12034@mindspring.com> (raw)
In-Reply-To: <3C0E4487.6000704@savoirfairelinux.com> <3C0E4803.3BBF045B@didntduck.org> <3C0E7CCD.F9553BBD@nortelnetworks.com>
In-Reply-To: <3C0E7CCD.F9553BBD@nortelnetworks.com> from Christopher Friesen on 12/05/2001 14:00
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On 12/05/2001 15:00 -0500, Christopher Friesen wrote:
>> Couldn't you use mlockall() to ensure that demand paging is not a factor? Then
>> you should be able to free up the disk space since the actual application is
>> guaranteed to be in ram.
>>
mlockall() only locks those pages that are **currently** paged
in, or optionally those that will be paged in in the future.
Unless you have a way to make sure that all pages of the
binary are actually in memory before you call mlockall(),
this gains you nothing.
--
twalberg@mindspring.com
[-- Attachment #2: Type: application/pgp-signature, Size: 175 bytes --]
next prev parent reply other threads:[~2001-12-05 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 16:00 Removing an executable while it runs Cyrille Beraud
2001-12-05 16:14 ` Brian Gerst
2001-12-05 20:00 ` Christopher Friesen
2001-12-05 20:54 ` Tim Walberg [this message]
2001-12-06 0:25 ` Jeff Dike
2001-12-06 15:43 ` Eric-Olivier Lamey
-- strict thread matches above, loose matches on Subject: below --
2001-12-05 17:15 Petr Vandrovec
2001-12-05 19:32 ` Mike Fedyk
2001-12-05 21:19 Petr Vandrovec
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=20011205145442.A12034@mindspring.com \
--to=twalberg@mindspring.com \
--cc=bgerst@didntduck.org \
--cc=cfriesen@nortelnetworks.com \
--cc=cyrille.beraud@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.