You've accounted for 3.2M(pidin in might consider this to be 4M?) of the
6M in /dev/shmem(which doesn't show up in pidin -f ncd), and the
granularity of pidin in is 1M(I believe it rounds down) ...


Try the following to get a more accurate view of the memory in use:

#include <errno.h>
#include <stdint.h>
#include <unistd.h>
#include <stdarg.h>
#include <stdlib.h>
#include <stdio.h>
#include <string.h>
#include <sys/stat.h>
#include <sys/syspage.h>

uint64_t
get_free_mem (void)
{
        int ret;
        struct stat64 sbuf;
        ret = stat64("/proc", &sbuf);
        if (ret == -1) {
                printf("stat(/proc) failed: %s", strerror(errno));
        }
        return sbuf.st_size;
}

uint64_t
get_total_mem (void)
{
        char *str = SYSPAGE_ENTRY(strings)->data;
        struct asinfo_entry     *as = SYSPAGE_ENTRY(asinfo);
        uint64_t total = 0;
        unsigned num;

        for (num = _syspage_ptr->asinfo.entry_size / sizeof(*as); num >
0; --num) {
                if(strcmp(&str[as->name], "ram") == 0) {
                        total += as->end - as->start + 1;
                }
                ++as;
        }
        return total;
}

int
main (int argc, char **argv)
{
        uint64_t free_mem = get_free_mem();
        uint64_t total_mem = get_total_mem();
        printf("FreeMem/TotalMem: %llu/%llu\n", free_mem,total_mem );
        printf("Total Mem In Use: %llu bytes\n",total_mem-free_mem );
        return EXIT_SUCCESS;
}



-----Original Message-----
From: Pavol Kycina [mailto:community-noreply@qnx.com] 
Sent: Wednesday, September 16, 2009 2:58 PM
To: ostech-core_os
Subject: Re: RE: RE: pidin in memory info

I have compared output from pidin mem from both systems.

These are the only differences:
Sept
  704549   1 bin/sh              10r REPLY            144K  108K
8192(516K)*
  360471   1 bin/login           10r REPLY             16K   72K
8192(516K)*
  315414   6 bin/io-net          10r RECEIVE           64K  476K
4096(68K)
  315414   5 bin/io-net          21r RECEIVE           64K  476K
4096(132K)
  315414   4 bin/io-net          10r RECEIVE           64K  476K
4096(68K)
  315414   3 bin/io-net          10r RECEIVE           64K  476K
4096(68K)
  315414   2 bin/io-net          10r RECEIVE           64K  476K
4096(132K)
  315414   1 bin/io-net          10r SIGWAITINFO       64K  476K
8192(516K)*
 
August
  835637   1 bin/login           10r REPLY             16K   72K
8192(516K)*
  835608   1 bin/login           10r REPLY             16K   72K
8192(516K)*
  761892   1 cpuLoad             10r NANOSLEEP         12K  104K
12K(516K)*
  368662   6 bin/io-net          10r RECEIVE           64K  516K
4096(68K)
  368662   5 bin/io-net          21r RECEIVE           64K  516K
4096(132K)
  368662   4 bin/io-net          10r RECEIVE           64K  516K
4096(68K)
  368662   3 bin/io-net          10r RECEIVE           64K  516K
4096(68K)
  368662   2 bin/io-net          10r RECEIVE           64K  516K
4096(132K)
  368662   1 bin/io-net          10r SIGWAITINFO       64K  516K
8192(516K)*


> Using pidin -f ncd doesn't show the whole picture, each thread has a
> stack that also contributes to the total memory in use in the system.
> Use "pidin mem"
> 
> 
> -----Original Message-----
> From: Pavol Kycina [mailto:community-noreply@qnx.com] 
> Sent: Wednesday, September 16, 2009 9:48 AM
> To: ostech-core_os
> Subject: Re: RE: pidin in memory info
> 
> > When you say almost the same memory sizes are you referring to the
> > output from "pidin mem"?  Also, what version are you using?
> 
> pidin -f ncd
> 
> version 6.3.2 (on both systems)
> 
> > 
> > 
> > -----Original Message-----
> > From: Alexander Koppel [mailto:community-noreply@qnx.com]...