On Wed, Aug 4, 2010 at 12:24 PM, Steven Dake <[email protected]> wrote:
> On 08/03/2010 10:02 AM, hj lee wrote: > >> >> 2. Shared memory increases whenever pacemaker resource is started or >> stopped. In this case, cib's shared memory also increases. I highly >> suspect this leak comes from mmap in corosync ipc code. >> [r...@silverthorne4 epel]# top -b -n1 | egrep "coro|cib|attrd" >> 16579 root RT 0 207m 4316 2036 S 0.0 0.1 0:00.11 corosync >> 16587 hacluste -8 0 69048 4596 2584 S 0.0 0.1 0:00.39 cib >> 16589 hacluste -8 0 69808 2436 2024 S 0.0 0.1 0:00.00 attrd >> >> [r...@silverthorne4 epel]# crm resource stop faultymon-clone >> >> [r...@silverthorne4 epel]# top -b -n1 | egrep "coro|cib|attrd" >> 16579 root RT 0 207m 4336 2056 S 0.0 0.1 0:00.13 corosync >> 16587 hacluste -8 0 69068 4620 2596 S 0.0 0.1 0:00.41 cib >> 16589 hacluste -8 0 69808 2436 2024 S 0.0 0.1 0:00.00 attrd >> >> Thanks >> hj >> >> > corosync doesn't leak without pacemaker. > > The major difference in pacemaker is the use of fork. Angus, one thing to > try is madvise (DONTFORK) on the mmap sections. > Hi, It's clear both RES and SHR at top command keeps increasing. But I am not sure this is a really memory leak or not. It seems that these RES and SHR in top is not correct. It does not seem reflect the actual resident memory of a process. Some people in the web say that RES - SHR is actual resident memory used by process. In above, RES-SHR = 2280, it's constant. Any body has a good idea on SHR in top is calculated or how kernel updates RES of a process? hj
_______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
