[Fwd: LINUX-MM]
--
*****************************************************************
* Matthias Arnold
* Klinikum der Friedrich-Schiller-Universitaet
* Institut fuer Med. Statistik, Informatik und Dokumentation
* Jahnstrasse 3
* D-07743 Jena
*
* email:[email protected]
* Tel. :+49-3641-934130
* FAX :+49-3641-933200
******************************************************************
Quoted 12 lines · Stephen C. Tweedie
Hi,
Quoted 7 lines · Kev
Quoted 4 lines
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.
Quoted 6 lines
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:[email protected]
* Tel. :+49-3641-934130
* FAX :+49-3641-933200
******************************************************************
Quoted 13 lines
Quoted 13 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
"MA" == Matthias Arnold <[email protected]> writes:
Quoted 7 lines · Kev
Quoted 4 lines
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.
Quoted 6 lines
Quoted 6 lines
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 [email protected]. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
Quoted 13 lines
Quoted 13 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
"MA" == Matthias Arnold <[email protected]> writes:
Quoted 7 lines · Kev
Quoted 4 lines
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.
Quoted 6 lines
Quoted 6 lines
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 [email protected]. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/