glibc........ memory limitations.... ideas?
kd at flaga.is
kd at flaga.is
Thu Oct 21 21:29:20 EST 1999
I am no expert but DRAM takes a lot of current when you access it. And I
suspect that if you double the memory size the refresh cycle current is
So if you have the fs also in DRAM you essentially make memory accesses
more frequently and therfore you draw more current.
I made a quick measurement on the 4MB simm, no parity, 5V I have in my
board and it looks like the DRAM is drawing something like 10mA just in
refresh cycle (no memory accesses).
When the kernel has booted it is drawing close to 110mA. And as I
understand from the HW-engeneers 100mA is alot!! 8-)
I suspect that it is possible to "strip down" glibc. But I have no Idea how
much work that is.
Has anyone any experience with NewLib? Do you think it is easy to mix
pthread or LinuxThreads and NewLib and stdlibc++?
Dan Malek <dan at netx4.com>
Sent by: To: kd at flaga.is
owner-linuxppc-embedded at lists.li cc: linuxppc-embedded at lists.linuxppc.org
nuxppc.org Subject: Re: glibc........ memory limitations.... ideas?
10/20/99 07:18 PM
kd at flaga.is wrote:
> Compressed filesystems is one option but that means we have to increase
> size of the DRAM and that again means increased current drain. Limited
> battery resources is
> one of our contraints also.
Just because I need to learn something today, does memory really take
that much power?
> How do you guys cram all the software you want into so small space?
I am still using the old R4 libc-1.99 and associated libararies
for this reason.
One of the differences is that glibc2 just simply has more stuff
in it, which was contained in separate libraries of the past. If
you want lots of the workstation features in your embedded system,
you will still end up with lots of library space used.
> ... Are
> there any othre c and c++ libraries that are smaller but provides access
> threads (pthreads) and
> work with linux?
Here again, I am a minimalist. I don't use pthreads, as the
implementation is very heavyweight. I just use Linux threads and
some simple atomic operations for synchronization. I certainly
don't use C++ in a resource constrained embedded environment.
All of my embedded applications have used compressed ram disks
in Flash rom....It doesn't take long before you have an application
that needs a temporary file of some kind.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-embedded