On Wed, Nov 2, 2016 at 8:46 PM, Nicholas Piggin <npiggin@xxxxxxxxx> wrote:
>
> If you don't have that, then a long-waiting waiter for some
> unrelated page can prevent other pages from getting back to
> the fastpath.
>
> Contention bit is already explicitly not precise with this patch
> (false positive possible), but in general the next wakeup will
> clean it up. Without page_match, that's not always possible.
Do we care?
The point is, it's rare, and if there are no numbers to say that it's
an issue, we shouldn't create the complication. Numbers talk,
handwaving "this might be an issue" walks.
That said, at least it isn't a big complexity that will hurt, and it's
very localized.
>> Also, it would be lovely to get numbers against the plain 4.8
>> situation with the per-zone waitqueues. Maybe that used to help your
>> workload, so the 2.2% improvement might be partly due to me breaking
>> performance on your machine.
>
> Oh yeah that'll hurt a bit. The hash will get spread over non-local
> nodes now. I think it was only a 2 socket system, but remote memory
> still takes a latency hit. Hmm, I think keeping the zone waitqueue
> just for pages would be reasonable, because they're a special case?
HELL NO!
Christ. That zone crap may have helped some very few NUMA machines,
but it *hurt* normal machines.
So no way in hell are we re-introducing that ugly, complex, fragile
crap that actually slows down the normal case on real loads (not
microbenchmarks). It was a mistake from the very beginning.
No, the reason I'd like to hear about numbers is that while I *know*
that removing the crazy zone code helped on normal machines (since I
could test that case myself), I still am interested in whether the
zone removal hurt on some machines (probably not two-node ones,
though: Mel already tested that on x86), I'd like to know what the
situation is with the contention bit.
I'm pretty sure that with the contention bit, the zone crud is
entirely immaterial (since we no longer actually hit the waitqueue
outside of IO), but my "I'm pretty sure" comes back to the "handwaving
walks" issue.
So numbers would be really good.
Linus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>