Process memory

[Anil SB]

> I am referring to the committed memory size not RSS.

IMU - you could get the committed_as for the entire system easily
(using "grep Committed_AS /proc/meminfo"), normally its the kernel
responsibility to keep track of the over-committed memory, the process
will not get to see an actual increase in RSS unless the process
starts using the requested / malloc()-ed memory. It should be possibly
to notice an increase in VIRT (from top) or VSZ (valgrind) when the
committed_AS for a process goes up.


On Thu, Jun 5, 2014 at 3:40 PM, Pratap kommula <pratapkommula at gmail.com> wrote:
> I am referring to the committed memory size not RSS.
>
> Thanks,
> Rammohan
>
>
> On Thu, Jun 5, 2014 at 12:20 PM, Mulyadi Santosa <mulyadi.santosa at gmail.com>
> wrote:
>>
>> On Thu, Jun 5, 2014 at 1:35 PM, Pratap kommula <pratapkommula at gmail.com>
>> wrote:
>> > Hi,
>> >
>> > How do we know that how much memory allocated for a process and how to
>> > set a
>> > limit on it?
>>
>> Are you referring to resident set size or committed memory size?
>>
>>
>> Mulyadi Santosa
>> Freelance Linux trainer and consultant
>>
>> blog: the-hydra.blogspot.com
>> training: mulyaditraining.blogspot.com
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>