Dan Sugalski <[EMAIL PROTECTED]> wrote:
struct hunk { struct pobj header; INTVAL used; INTVAL avail;
Only one of these is needed (and currently used: "used")
struct hunk *upchain; struct regframe RegisterFrame[FRAMES_PER_HUNK];
I'd rather not have the store statically inside the hunk: - small objects code currently has an upper limit for sized header pools
Doesn't mean we have to use them, honestly. A separate arena for them is fine.
- more and differently sized pools impose negative effects on DOD times
While true, we're already walking the stack frame areas, so I'm not sure it'll work out that way.
- it needs more code duplication
True, unless we yank out existing special-purpose code. If stack frame PMCs end up looking to the DOD like array PMCs, well... less code to deal with, since we'll be using the array code that already exists. The tradeoff is code in the allocator, but I'm not sure it'll actually be more code, just different code.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
