lkml.org 
[lkml]   [2008]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectx86: Is there still value in having a special tlb flush IPI vector?
Now that normal smp_function_call is no longer an enormous bottleneck, 
is there still value in having a specialised IPI vector for tlb
flushes? It seems like quite a lot of duplicate code.

The 64-bit tlb flush multiplexes the various cpus across 8 vectors to
increase scalability. If this is a big issue, then the smp function call
code can (and should) do the same thing. (Though looking at it more
closely, the way the code uses the 8 vectors is actually a less general
way of doing what smp_call_function is doing anyway.)

Thoughts?

(And uv should definitely be hooking pvops if it wants its own
flush_tlb_others; vsmp sets the precedent for a subarch-like use of pvops.)

J


\
 
 \ /
  Last update: 2008-07-29 01:19    [W:0.067 / U:0.560 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site