|
From: Erik W. <om...@cs...> - 2000-04-28 06:48:40
|
On Thu, 27 Apr 2000, James Bowman wrote:
> I took a look at module sizes and found that we're at about 16k of text:
> we're blowing the code cache, and when code moves around (like when you
> remove a module) different functions are cacheing against each other and
> changing performance in surprising ways.
Whee! ;-)
> The code should get smaller as we optmize it, though, so this effect
> will go away. We should be safe if the decode loop fits in 12k.
Yeah, we can do that pretty easily. Eventually I expect that a sufficient
percentage of this will be written in ASM to keep it well below that.
Then of course we have to worry about blowing the data cache. That means
all sorts of tricks, most of which aren't set up yet (such as using
non-cachable pages, which means a kernel hack).
Erik Walthinsen <om...@cs...> - Staff Programmer @ OGI
Quasar project - http://www.cse.ogi.edu/DISC/projects/quasar/
Video4Linux Two drivers and stuff - http://www.cse.ogi.edu/~omega/v4l2/
__
/ \ SEUL: Simple End-User Linux - http://www.seul.org/
| | M E G A Helping Linux become THE choice
_\ /_ for the home or office user
|