Re: [PATCH 7/8] mm: thp: Use more portable PMD clearing sequenece in zap_huge_pmd().

2012-10-02 Thread Andrea Arcangeli
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

[PATCH 7/8] mm: thp: Use more portable PMD clearing sequenece in zap_huge_pmd().

2012-10-02 Thread David Miller
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

[PATCH 7/8] mm: thp: Use more portable PMD clearing sequenece in zap_huge_pmd().

2012-10-02 Thread David Miller
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

Re: [PATCH 7/8] mm: thp: Use more portable PMD clearing sequenece in zap_huge_pmd().

2012-10-02 Thread Andrea Arcangeli
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.