From: ebiederm+eric@ccr.net (Eric W. Biederman)
To: Matthias Arnold <Matthias.Arnold@edda.imsid.uni-jena.de>
Cc: linux-mm@kvack.org
Subject: Re: [Fwd: LINUX-MM]
Date: 24 Mar 1999 05:49:08 -0600 [thread overview]
Message-ID: <m1emmfxg3v.fsf@flinx.ccr.net> (raw)
In-Reply-To: Matthias Arnold's message of "Wed, 24 Mar 1999 08:42:02 +0100"
>>>>> "MA" == Matthias Arnold <Matthias.Arnold@edda.imsid.uni-jena.de> writes:
>>
>> 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.
MA> Thanks to the community for dealing with my problems.Before we go on to
MA> discuss this as bug or feature I emphasize
MA> that this memory effect is really disastrous for me.
MA> I hope that changing the kernel (as Rik told me) helps.
MA> Any suggestion is very welcome.
I missed the start of this, (I just monitor linux-mm),
what is the problem you have?
Eric
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-03-24 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-24 7:42 [Fwd: LINUX-MM] Matthias Arnold
1999-03-24 11:49 ` Eric W. Biederman [this message]
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=m1emmfxg3v.fsf@flinx.ccr.net \
--to=ebiederm+eric@ccr.net \
--cc=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 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.