* Ingo Molnar <mi...@kernel.org> wrote:
> [...]
>
> Rik, mind sending an updated patch that addresses Linus's
> concerns, or should I code it up if you are busy?
>
> We can also certainly try the second patch, but I'd do it at
> the end of the series, to put some tree distance between the
> two patches, to not concentrate regression risks too tightly
> in the Git space, to help out with hard to bisect problems...
I'd also like to have the second patch separately because I'd
like to measure spurious fault frequency before and after the
change, with a reference workload.
Just a single page fault, even it's a minor one, might make a
micro-optimization a net loss. INVLPG might be the cheaper
option on average - it needs to be measured. (I'll do that, just
please keep it separate from the main TLB-flush optimization.)
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
