David,
I suspect your doors arrangement is a losing proposition. A doors call is
cheap relative to many IPC methods, but expensive relative to the TLB miss
you are trying to avoid. A doors call costs a handful of microseconds or more.
A TLB miss takes approx 30 cycles for a TSB hit when the TT
Wow, thanks for the fast feedback, guys. Sorry about the insufficient detail...
I've work with Sun stuff for so long I keep forgetting about the AMD stuff.
The hardware this stuff runs on is mostly USIII and IIIi, basically
Netra/Sunfire 1280 and 440 boxes. The app is currently 32 bits. We're p
David McDaniel wrote:
Being insufficiently familiar with kernel goings-on, I've yet to
find the answer to what someone more familiar may know off the top of the head.
Are the TLB contents saved and restored across context switches?
On SPARC, TLB entries are tagged w/ the context that created
On Thu, Jun 29, 2006 at 10:21:20AM -0700, David McDaniel wrote:
> Being insufficiently familiar with kernel goings-on, I've yet to find the
> answer to what someone more familiar may know off the top of the head.
> Are the TLB contents saved and restored across context switches? Or
> are they si
David McDaniel wrote:
Being insufficiently familiar with kernel goings-on, I've yet to find the
answer to what someone more familiar may know off the top of the head.
Are the TLB contents saved and restored across context switches? Or are they
simply invalidated and lazily restored upon threa
Being insufficiently familiar with kernel goings-on, I've yet to find the
answer to what someone more familiar may know off the top of the head.
Are the TLB contents saved and restored across context switches? Or are they
simply invalidated and lazily restored upon thread resumption? Or somethi
