> > Pardon if this has come up before, but what about the greatly
> > increased time taken to launch a shared-lib program? That's quite
>
> Not that much if your loaded caches the binaries of the programs (as
> we do) and they
> are small and for really shared state you have filesystems which
> s
> #include
> #include
> int main(void){exits(nil);}
>
> is 3317 bytes on my atom box.
Bloatware! A quick visit to 6th edition Unix (on 32-bit Interdata)
via the SIMH time machine produces this:
# cat >t.c
int main() {exit(0);}
# cc t.c
# ls -l a.out
-rwxrwxrwx 1 root 164 Jun 4 15:53 a.o
On Fri, Oct 30, 2009 at 12:25 AM, Ethan Grammatikidis
wrote:
> On Thu, 29 Oct 2009 21:25:59 +0100
> Enrico Weigelt wrote:
> Pardon if this has come up before, but what about the greatly
> increased time taken to launch a shared-lib program? That's quite
Not that much if your loaded caches the
> contrast /386/bin/sleep, a non-trivial
> executable, at 4422 bytes on my system — 100x smaller.
#include
#include
int main(void){exits(nil);}
is 3317 bytes on my atom box.
insightful post
> Pardon if this has come up before, but what about the greatly
> increased time taken to launch a shared-lib program? That's quite
i just built a trivial executable on linux x86-64 with a
main that calls exit(0) as its only action. the
executable is 722905 bytes (which is large
On Thu, 29 Oct 2009 21:25:59 +0100
Enrico Weigelt wrote:
> Russ Cox wrote:
>
> Hi,
>
> >> Assuming statically linked-in libraries are properly aligned,
> >> we'll have lots of equal pages in the system, so the kernel could
> >> find and automatically map them together.
> >
> > This is not true
Russ Cox wrote:
Hi,
>> Assuming statically linked-in libraries are properly aligned,
>> we'll have lots of equal pages in the system, so the kernel could
>> find and automatically map them together.
>
> This is not true. When static libraries are linked into
> a target binary, only the necessar
> Assuming statically linked-in libraries are properly aligned,
> we'll have lots of equal pages in the system, so the kernel could
> find and automatically map them together.
This is not true. When static libraries are linked into
a target binary, only the necessary objects are taken,
and all th
On Sat, Apr 18, 2009 at 07:05:07PM +0200, Enrico Weigelt wrote:
>
> Assuming statically linked-in libraries are properly aligned,
> we'll have lots of equal pages in the system, so the kernel could
> find and automatically map them together.
>
Well that's one of the 3 classical options:
1) sta
Hi folks,
some time ago, we had several discussions about shared libraries,
mmap(), etc. One of the major arguments for shared libraries is
to share code pages between processes - and the traditional *nix
approach to do so is mmap() (at least on the systems I know).
Assuming statically linked-
10 matches
Mail list logo
