On Sat, 30 Jun 2001, Shane Nay wrote:
> On Saturday 30 June 2001 16:14, Risto J�rvinen wrote:
> > Have you considered using unix domain sockets for client-server
> > communications?
>
> Config option makes sense mostly for cutting down on kernel size.
I did a preliminary measurement with Linux/x86 kernel 2.4.5, minimal setup
and compiled two similar kernels but with the other without TCP protocol.
Networking was enabled but I removed networking devices and all that I
thought would depend on TCP and thus be removed with TCP and distort the
results.
Without TCP:
System is 481 kB
-rw-r--r-- 1 root root 496215 Jul 1 11:02 bzImage
-rwxr-xr-x 1 root root 1519072 Jul 1 11:02 vmlinux
With TCP:
System is 572 kB
-rw-r--r-- 1 root root 589503 Jul 1 11:07 bzImage
-rwxr-xr-x 1 root root 1747611 Jul 1 11:07 vmlinux
Around 90kB difference might not seem much on x86 but I bet extra 90kBs
would be handy in a heavily constrained embedded solution that doesn't
need TCP otherwise. (Think of Helio and the pitiful 2MB+8MB) Though YMMV,
this measurement is by no means reliable.
Since the change in behavior is really minimal (only changing few lines of
code where socket is created, bound and connected) I'd say it's worth it.
While I'm at it, I'd recommend trying to port PicoGUI to uClibc. glibc2
is bloated (libuClibc.so is only ~150kB). OTOH uClibc is limited but at
least busybox runs under it, so why not PicoGUI too. Though at the moment
there is only partial MIPS port of it (considering Helio again). Someone
with understanding of libc should cut-paste/hack the platform depended
parts from glibc2. (But as I see you're already active on the uClibc
developer list, I guess you've thought about this already :-) )
- Riba
>
> Thanks,
> Shane Nay.
>
_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/pgui-devel
