From: Matthias Arnold <Matthias.Arnold@edda.imsid.uni-jena.de>
To: linux-mm@kvack.org
Subject: [Fwd: LINUX-MM]
Date: Wed, 24 Mar 1999 08:42:02 +0100 [thread overview]
Message-ID: <36F8974A.D4EB4BAD@imsid.uni-jena.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
--
*****************************************************************
* Matthias Arnold
* Klinikum der Friedrich-Schiller-Universitaet
* Institut fuer Med. Statistik, Informatik und Dokumentation
* Jahnstrasse 3
* D-07743 Jena
*
* email:iia@imsid.uni-jena.de
* Tel. :+49-3641-934130
* FAX :+49-3641-933200
******************************************************************
[-- Attachment #2: Type: message/rfc822, Size: 1904 bytes --]
From: Matthias Arnold <Matthias.Arnold@imsid.uni-jena.de>
To: "Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: LINUX-MM
Date: Wed, 24 Mar 1999 08:35:32 +0100
Message-ID: <36F895C4.1801DBE6@imsid.uni-jena.de>
Stephen C. Tweedie wrote:
> Hi,
>
> On Tue, 23 Mar 1999 10:49:11 EST, Kev <klmitch@MIT.EDU> said:
>
> >> IIRC there's a slight bug in some of the newer kernels
> >> where the swap cache isn't being freed when you exit
> >> your program, but only later on when the system tries
> >> to reclaim memory...
>
> > I believe the problem lies in the fact that there is not enough
> > SysV shared memory available.
>
> It's nothing to do with SysV shared memory.
>
> The behaviour is there, but the only impact on the normal user will be
> that "free" lies a little. No big deal: it just shows up as cache. The
> effect is only a matter of when we recover the memory, not whether we
> recover it.
Thanks to the community for dealing with my problems.Before we go on to
discuss this as bug or feature I emphasize
that this memory effect is really disastrous for me.
I hope that changing the kernel (as Rik told me) helps.
Any suggestion is very welcome.
Matthias
--
*****************************************************************
* Matthias Arnold
* Klinikum der Friedrich-Schiller-Universitaet
* Institut fuer Med. Statistik, Informatik und Dokumentation
* Jahnstrasse 3
* D-07743 Jena
*
* email:iia@imsid.uni-jena.de
* Tel. :+49-3641-934130
* FAX :+49-3641-933200
******************************************************************
next reply other threads:[~1999-03-24 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-24 7:42 Matthias Arnold [this message]
1999-03-24 11:49 ` Eric W. Biederman
1999-03-24 12:04 ` Eric W. Biederman
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=36F8974A.D4EB4BAD@imsid.uni-jena.de \
--to=matthias.arnold@edda.imsid.uni-jena.de \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox