On Tue, Oct 02, 2012 at 06:27:41PM -0400, David Miller wrote:
>
> Invalidation sequences are handled in various ways on various
> architectures.
>
> One way, which sparc64 uses, is to let the set_*_at() functions
> accumulate pending flushes into a per-cpu array. Then the
> flush_tlb_range() et
Invalidation sequences are handled in various ways on various
architectures.
One way, which sparc64 uses, is to let the set_*_at() functions
accumulate pending flushes into a per-cpu array. Then the
flush_tlb_range() et al. calls process the pending TLB flushes.
In this regime, the
Invalidation sequences are handled in various ways on various
architectures.
One way, which sparc64 uses, is to let the set_*_at() functions
accumulate pending flushes into a per-cpu array. Then the
flush_tlb_range() et al. calls process the pending TLB flushes.
In this regime, the
On Tue, Oct 02, 2012 at 06:27:41PM -0400, David Miller wrote:
Invalidation sequences are handled in various ways on various
architectures.
One way, which sparc64 uses, is to let the set_*_at() functions
accumulate pending flushes into a per-cpu array. Then the
flush_tlb_range() et al.
4 matches
Mail list logo