[Fwd: LINUX-MM]

[Fwd: LINUX-MM]

[Matthias Arnold]

[-- 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
******************************************************************

Re: [Fwd: LINUX-MM]

[Eric W. Biederman]

>>>>> "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/

Re: [Fwd: LINUX-MM]

[Eric W. Biederman]

>>>>> "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/