Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 27 Jun 2011 17:37:39 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: Anti-bloat side project

On Mon, Jun 27, 2011 at 11:38:05PM +0200, Szabolcs Nagy wrote:
> * Rich Felker <dalias@...ifal.cx> [2011-06-27 17:19:09 -0400]:
> > Bleh. Has there been any serious work to document the causes and how
> > the code could be changed to fix the syscall bloat though? Or just
> > preliminat strace and wc -l?
> 
> most of the syscalls are due to python module imports check
> 100 different locations before finding the good one
> 
> imho they measured it and concluded that with modern
> filesystem caching this does not matter much..

Well they're wrong. Even if the syscall did nothing but enter and
leave kernelspace, it would still be very expensive. Using a module
cache/registry of some sort could solve the problem, or they could
first tackle all the non-open() syscalls which still make up a heavy
share of the cost..

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.