On Friday 15 November 2013 16:54:03 Bastian Bittorf wrote: > * Sven Eckelmann <s...@open-mesh.com> [11.11.2013 11:41]: > > On Friday 08 November 2013 11:32:23 Weedy wrote: > > > Do you have any benches or log dumps that show this fixed it for you? > > > > I am not really sure what you are expecting. I can not really show a log > > of > > the reset because the device just resets when the oom kicks in or the > > process is just killed (so it is really boring). And the log of a working > > system is also extreme boring. What do you want to see when nothing > > happens? > maybe you can show something on the commandline > bye forking and forking and show the mem-usage of the tasks?
Forking doesn't make a lot of sense because this is related to the NPTL stack
cache of a single process (so it is only related to pthreads). But the output
of an example thread test is relative unspectacular: nodogsplash 0.9_beta9.9.6
on a 32 MiB MIPS device starts with ~25% memory usage for this particular
process and increases more and more up to ~150% (so it is overbooking). With
all changes applied it stays at ~9%
Kind regards,
Sven
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
