You can do a very crude listing of RSS (resident set size) using grep:

# grep RSS /proc/*/status
1/status:VmRSS:      604 kB
10413/status:VmRSS:      496 kB
1241/status:VmRSS:      1412 kB
1273/status:VmRSS:       684 kB
1308/status:VmRSS:       412 kB
1318/status:VmRSS:       364 kB
1386/status:VmRSS:       552 kB
1654/status:VmRSS:       452 kB
1768/status:VmRSS:       660 kB
1810/status:VmRSS:       648 kB
1949/status:VmRSS:       404 kB
447/status:VmRSS:      276 kB
448/status:VmRSS:      212 kB
6496/status:VmRSS:       496 kB
6497/status:VmRSS:       452 kB
self/status:VmRSS:       384 kB

But as David said, best is to install procps if you have space.

On Thu, Jun 26, 2014 at 12:17 AM, Le Tran Dat <[email protected]> wrote:
> Thank David.
>
>
> On Thu, Jun 26, 2014 at 11:59 AM, David Madden <[email protected]> wrote:
>>
>> On 6/25/14, 8:48 PM, Le Tran Dat wrote:
>> > my `ps` only supports w
>>
>> Ah, sorry.  I always change to the real proc-utils, rather than Busybox.
>>  But "ps -w" tells you what you need to know.
>>
>> > However, it does not show every application
>>
>> Do you mean, "why are some of the VSZ values zero?"
>>
>> > root@MimoAP:/# ps -w
>> >   PID USER       VSZ STAT COMMAND
>> >     1 root      1512 S    init
>> >     2 root         0 SW    [kthreadd]
>>
>> I'm not 100% sure, but I think the ones that are "0" are using
>> preallocated / locked kernel memory.  They're kernel threads, so you
>> can't kill them (or, at least, you can't free any memory by killing them).
>>
>> The VSZ is probably somewhat misleading also: it's the VIRTUAL size,
>> rather than the run-set size (which is the actual RAM in use at any
>> time).  Also, a lot of the processes probably share the C or network
>> libraries, so even if you have several 1.5MB processes, they might use
>> much less memory than you think because a lot of it is shared between
>> them.
>>
>> You might want to compile the non-busybox proc tools to get more
>> information.
>>
>> You can probably also get the information directly from the /proc files,
>> but I don't know how to interpret those directly -- I always rely on the
>> utilities.
>>
>> --
>> Mersenne Law LLP  ·  www.mersenne.com  ·  +1-503-679-1671
>> - Small Business, Startup and Intellectual Property Law -
>> 9600 S.W. Oak Street · Suite 500 · Tigard, Oregon  97223
>>
>
>
> _______________________________________________
> openwrt-users mailing list
> [email protected]
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
>
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users

Reply via email to