From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jody Bruchon <jody@jodybruchon.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Condensing and re-coding programs to save space
Date: Tue, 28 Feb 2017 21:12:38 +0000 [thread overview]
Message-ID: <20170228211238.3ff756ce@www.etchedpixels.co.uk> (raw)
In-Reply-To: <a2dc19af-7fba-5e2b-7781-752c5c0700c8@jodybruchon.com>
You could take a look at the FUZIX userspace. Much of it is far more
compact and a lot of it uses write() etc for size saving. The library
routines are also often a lot more memory efficient (eg the malloc is
much tinier as it was rewritten after I found the ELKS one was being
really buggy).
There shouldn't be too much churn involved as the FUZIX libc is based in
part on the ELKS one with other bits taken from MUSL and the like (and
the FP library largely comes from the Sun contributions)
A second option for the C library is to implement shared libraries not
necessarily by truely sharing it as a library with its own cs: but using
the callers ds:/ss:, as that involves some fun for fixing up callbacks,
but even something as simple as loading it into the process address space
from a different file when execve runs.
And the third of course is to implement support for something like
exomizer, that doesn't even need kernel support except for split I/D
binaries.
The compressor needs a big computer but the decompressor is tiny.
Alan
prev parent reply other threads:[~2017-02-28 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 19:53 Condensing and re-coding programs to save space Jody Bruchon
2017-02-27 22:02 ` Marc-F. LUCCA-DANIAU
2017-02-27 22:11 ` Jody Bruchon
2017-02-28 9:31 ` Marc-François LUCCA-DANIAU
2017-02-28 11:54 ` Georg Potthast 2
2017-02-28 12:17 ` Jody Bruchon
2017-02-28 21:12 ` Alan Cox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170228211238.3ff756ce@www.etchedpixels.co.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jody@jodybruchon.com \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).