Jeff Bacon wrote: > On 4/21/2010 11:25 AM, Lennart Sorensen wrote: > > On Wed, Apr 21, 2010 at 11:21:19AM -0400, Jeff Bacon wrote: > > > >> What version of Busybox are you using? I am finding it difficult to make > >> a newer version (1.15.x, 1.16.0) that small. In fact, when I configure > >> it with a single applet, I still somehow get a ~200kB binary. Are there > >> other options you are using in the build process to make your BB binary > >> so small? > >> > > 1.16.0. I didn't say the binary is that small. I said the variable data > > size is that size. When loading a FLAT binary, the kernel allocated one > > chunk for the binary (usually shared with existing copies if possible, > > which is great for busybox cases of course), and another for the variable > > data (heap, stack, etc). It was the variable data that is allocated per > > instance that I got that small. Turning on tracing in the FLAT binary > > using flthdr makes the kernel tell you when running things how much it > > is using. > > > > The busybox binary is 264KB in my case (with is using a FLAT with data > > compression enabled). > > > > > I was under the impression that for NOMMU, binary Text segments could > NOT be shared. How are you getting the kernel to share the text areas? > For me, every copy of BB is taking up a new 256kB chunk. I am running > on an ARM7TDMI, you?
You can use XIP in RAM on ARM7TDMI to share text segments. On other arches, FD-PIC also works, but not on ARM at present. -- Jamie _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev