Armin Rigo wrote: > Hello, > > In summary, we need to: > > - cache possibly more than one frame per code object; > - free old frames for code objects that haven't been run for a while. > > At this point I need more thinking. If someone comes up with an elegant way > to do both (as opposed, say, to abusing a lot of fields to put PyFrameObject > structures into two linked lists at the same time), he'd be welcome :-) What's bad about my proposal? In short: No frame cache in the code object. Have a small array of chains of cached frames. Index this by the address of the code object modulo some prime which is the array size. -- Christian Tismer :^) <mailto:tismer at stackless.com> Mission Impossible 5oftware : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 89 09 53 34 home +49 30 802 86 56 mobile +49 173 24 18 776 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4