From: Arno Euteneuer <Arno.Euteneuer@toptica.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] sporadic crashes of shell commands
Date: Fri, 17 Jan 2014 12:50:45 +0000 [thread overview]
Message-ID: <49BD654B8E52F64BBC06DF3F86638DFAF5A035@MSE1MUC.toptica.com> (raw)
In-Reply-To: <201401171215.46967.jbe@pengutronix.de>
Hi Jürgen,
> [...]
> Is there a correlation between the memory size the kernel gets reported
> and the used memory devices soldered onto the board? ;)
>
> [...]
>
I hope there is a very strong correlation ;-)
We have 256MB DDR2 RAM and 512MB NAND flash and get the following:
root@dlcpro:~ cat /proc/meminfo
MemTotal: 235876 kB
MemFree: 169852 kB
Buffers: 0 kB
Cached: 27988 kB
SwapCached: 0 kB
Active: 15648 kB
Inactive: 22560 kB
Active(anon): 10300 kB
Inactive(anon): 104 kB
Active(file): 5348 kB
Inactive(file): 22456 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 10248 kB
Mapped: 29924 kB
Shmem: 184 kB
Slab: 11100 kB
SReclaimable: 4848 kB
SUnreclaim: 6252 kB
KernelStack: 544 kB
PageTables: 336 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 117936 kB
Committed_AS: 73872 kB
VmallocTotal: 761856 kB
VmallocUsed: 27740 kB
VmallocChunk: 639888 kB
This looks very much the same with either of the kernels, independent of the used toolchain.
For me this looks ok, doesn't it? (Although I must admit I'm not really sure what VmallocTotal tells me and whether it is correct to be so large. Looks like RAM + Flash?)
Best regards
Arno
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-01-17 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 10:16 Arno Euteneuer
2014-01-17 10:45 ` Tim Niemeyer
2014-01-17 13:04 ` Arno Euteneuer
2014-01-20 7:49 ` Arno Euteneuer
2014-01-17 11:15 ` Jürgen Beisert
2014-01-17 12:50 ` Arno Euteneuer [this message]
2014-01-17 13:20 ` Jürgen Beisert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49BD654B8E52F64BBC06DF3F86638DFAF5A035@MSE1MUC.toptica.com \
--to=arno.euteneuer@toptica.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox