On Mon, Nov 12, 2018 at 6:43 PM Michel Dänzer <mic...@daenzer.net> wrote:
> On 2018-11-08 6:23 a.m., Marek Olšák wrote: > > Thanks a lot man. I'll reconsider this depending on the results I > receive. > > > > I may also just pin the Mesa threads and keep the app thread intact. It > > should perform OK with glthread, but not without glthread. > > > > Another option is to have the gallium and winsys threads "chase" the main > > thread within the CPU by changing the thread affinity based on getcpu(). > > While those are interesting ideas for the future, I'm afraid it's too > late for them for the 18.3.0 release (scheduled for November 21st IIRC). > > Please make sure the thread pinning code is disabled for the release, at > least by default. > I'm not sure what the best solution is, but pinning the threads to the L3 CCX has shown great potential on my Ryzen 5 2600 and it would be nice to explore the ideas presented by Marek or maybe understand, why the kernel scheduler prefers to put the threads on cores on different CCX. For example The Wicher 2 goes from 60 FPS to 70 FPS average and this is impressive. Tomb Raider just increases about 1 FPS (average 104 FPS) but this can be just noise and for sure not noticeable. Regards edmondo
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
