Dave Jones wrote:
On Wed, Apr 11, 2007 at 10:30:58PM -0700, Zachary Amsden wrote:
> In situations where page table updates need only be made locally, and there
> is no cross-processor A/D bit races involved, we need not use the heavyweight
> xchg instruction to atomically fetch and clear page
On Wed, Apr 11, 2007 at 10:30:58PM -0700, Zachary Amsden wrote:
> In situations where page table updates need only be made locally, and there
> is no cross-processor A/D bit races involved, we need not use the heavyweight
> xchg instruction to atomically fetch and clear page table entries.
On Wed, Apr 11, 2007 at 10:30:58PM -0700, Zachary Amsden wrote:
In situations where page table updates need only be made locally, and there
is no cross-processor A/D bit races involved, we need not use the heavyweight
xchg instruction to atomically fetch and clear page table entries.
Dave Jones wrote:
On Wed, Apr 11, 2007 at 10:30:58PM -0700, Zachary Amsden wrote:
In situations where page table updates need only be made locally, and there
is no cross-processor A/D bit races involved, we need not use the heavyweight
xchg instruction to atomically fetch and clear page
In situations where page table updates need only be made locally, and there
is no cross-processor A/D bit races involved, we need not use the heavyweight
xchg instruction to atomically fetch and clear page table entries. Instead,
we can just read and clear them directly.
This introduces a neat
In situations where page table updates need only be made locally, and there
is no cross-processor A/D bit races involved, we need not use the heavyweight
xchg instruction to atomically fetch and clear page table entries. Instead,
we can just read and clear them directly.
This introduces a neat
6 matches
Mail list logo
