Linus Torvalds wrote: > So the only case that ends up being fairly heavy may be a case that is > very uncommon in practice (only for unmapping shared mappings in > threaded programs or the lazy TLB case). I can think of one case where performance is considered quite important: mprotect() is used by several garbage collectors, including threaded ones. Maybe mprotect() isn't the best primitive for those anyway, but it's what they have to work with atm. -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Re: x86 ptep_get_and_clear question Kanoj Sarcar
- Re: x86 ptep_get_and_clear question Linus Torvalds
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Kanoj Sarcar
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Linus Torvalds
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Linus Torvalds
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Manfred Spraul
- Re: x86 ptep_get_and_clear question Jamie Lokier
- Re: x86 ptep_get_and_clear question Linus Torvalds
- Re: x86 ptep_get_and_clear question Manfred Spraul