About extendable stacks in non VM-system

[cola99 <cola99a@yahoo.com.tw>]

I don't understand what this say~~~~

Extendable stacks and heaps in a non-VM system: Even when you don’t
have a disk and have no intention of supporting full demand paging, it
can still be useful to grow an application’s stack and heap on demand
while monitoring its growth. In this case you’ll need the TLB to map
the stack/heap addresses, and you’ll use TLB miss events to decide
whether to allocate more memory or whether the application is out
of control.

and this 

in the EntryLO Valid bit
Refill TLB is optimized for speed and doesn’t want to check for special
case. When some further processing is needed before a program can use a page
referred to by the memory-held table, the memory-held entry can be left
marked invalid. After TLB refill, this will cause a different kind of trap,
invoking special processing without having to put a test in every software
refill event

I can't understant why ??

Or someone can recommand where can discuss "see mips run " this book~~~~

-- 
View this message in context: http://www.nabble.com/About-extendable-stacks-in-non-VM-system-tp20287845p20287845.html
Sent from the linux-mips main mailing list archive at Nabble.com.