Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - image size issues: (3 Items)
   
image size issues  
For our embedded device, we've seen the os image go from ~2Meg to >4Meg. In looking at the files, it appears that io-pkt
-v4 by itself has grown to 690k compared to ~100k for io-net with io-pkt-v6-hc coming in at a whopping 1420k. libcrypt.
so.1 is just under 1800k. Was the binary download compiled with debug on by any chance. Is it reasonable to assume that 
these will shrink in the beta/general release?

Thx,
Bill
RE: image size issues  
Hi Bill:

	A few things to keep in mind here.  Io-net is simply a middleware
entity that doesn't really do anything without a protocol plugged in, so you
also need to included npm-tcpip-v4.so (or v6.so) in the calculation when you
do the comparison. One of the downsides of io-pkt is that the IP stack is a
fundamental part of the stack and can't be separated out as was the case for
io-net.  This is obviously not a problem if you need the IP stack, but if
you only wanted to use QNET, for the time being, you'd have to live with the
additional footprint with the IP stack being part of your image.

The binaries built in the networking project haven't been stripped.  This
means that a lot of additional symbol information is included which isn't
needed.  (This can mean a difference of 100-200K).  They will be stripped
when shipped (or you can use the strip utility on them yourselves). That
being said, I still don't see quite the same sizes that you do for the
unstripped versions (possibly because I'm building from the trunk.  I'll
have to check that out).

  I get binary sizes of ~480k for v4, 860k for v4-hc and 1MB for v6-hc
(after I've stripped them).

io-net is ~70k.  npm-tcpip-v4.so is ~300k and v6 is ~730k, so you're looking
at ~370k for v4 and ~800k for v6 (io-net + stack). So the stack has
definitely grown in size (which is to be expected) by what appears to be
~25% for the binaries when you compare like with like (there isn't really an
io-net equivalent to v4-hc in io-net given that it includes ipsec as well as
WiFi).

The version of the stack that you use obviously makes a difference.  There
is a lot more functionality built into the v4-hc and v6-hc stack variants
(WiFi, ipsec, etc. etc.), and that doesn't come for free (:->).


	R.




-----Original Message-----
From: William Smith [mailto:bsmith@tridium.com] 
Sent: Thursday, January 03, 2008 3:18 PM
To: ionetmig-networking
Subject: image size issues

For our embedded device, we've seen the os image go from ~2Meg to >4Meg. In
looking at the files, it appears that io-pkt-v4 by itself has grown to 690k
compared to ~100k for io-net with io-pkt-v6-hc coming in at a whopping
1420k. libcrypt.so.1 is just under 1800k. Was the binary download compiled
with debug on by any chance. Is it reasonable to assume that these will
shrink in the beta/general release?

Thx,
Bill

_______________________________________________
io-net migration
http://community.qnx.com/sf/go/post4041
Re: RE: image size issues  
Robert,

Thanks for the quick reply. It just caught up with me when I started to exceed the size of our raw partition. As you 
stated, there is quite a bit of new functionality (like ipv6 and wifi) that is supported and that we are evaluating so  
I just need to try and strike the balance in the size of our image. I'll play with the strip utility for now just to get
 my image size down. Thanks again.

Bill