Leopold__ has quit [Remote host closed the connection]
Leopold_ has joined #panfrost
Leopold__ has joined #panfrost
Leopold_ has quit [Ping timeout: 480 seconds]
stipa is now known as Guest6815
stipa has joined #panfrost
Guest6815 has quit [Ping timeout: 480 seconds]
camus has quit []
camus has joined #panfrost
PaulFertser has joined #panfrost
<PaulFertser>
Hi there! Probably not important but very puzzling for me: I have RK3399 with Mali-T860 (in Pinebook Pro) running Mesa 22.3.6. With vblank_mode=0 es2gears_x11 on Xorg I get about 140 FPS, with es2gears_wayland under Sway I get about 750. Is this normal? Why is the difference so huge?
<PaulFertser>
(tests were made full-screen 1920x1080; on Wayland the results improve considerably when es2gears window is smaller, on Xorg they stay the same)
Cyrinux947 has quit []
Cyrinux947 has joined #panfrost
rasterman has joined #panfrost
underpantsgnome[m] has quit []
Cyrinux947 has quit []
Cyrinux947 has joined #panfrost
atler has joined #panfrost
nlhowell has joined #panfrost
nlhowell has quit [Ping timeout: 480 seconds]
nlhowell has joined #panfrost
nlhowell has quit [Ping timeout: 480 seconds]
nlhowell has joined #panfrost
nashpa has joined #panfrost
dliviu has quit [Ping timeout: 480 seconds]
pbrobinson has quit [Ping timeout: 480 seconds]
pbrobinson has joined #panfrost
nashpa has quit []
dliviu has joined #panfrost
simon-perretta-img has quit [Quit: Leaving]
simon-perretta-img has joined #panfrost
kinkinkijkin has joined #panfrost
cphealy has joined #panfrost
rasterman- has joined #panfrost
rasterman- has quit []
rasterman- has joined #panfrost
rasterman- has quit [Remote host closed the connection]
simon-perretta-img_ has joined #panfrost
rasterman has quit [Ping timeout: 480 seconds]
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img_ has quit [Ping timeout: 480 seconds]
rasterman has joined #panfrost
<CounterPillow>
panfrost on xorg is not fully accelerated iirc, but that's okay because nobody should be using xorg anymore
alyssa has quit [Quit: alyssa]
<PaulFertser>
CounterPillow: I'm not sure I understand, isn't DRI making it irrelevant? The DDX driver is modeset, it shouldn't be related at all.
Leopold__ has quit [Remote host closed the connection]
thaytan has quit [Remote host closed the connection]
thaytan has joined #panfrost
dliviu has quit [Ping timeout: 480 seconds]
stepri01 has quit [Quit: leaving]
dliviu has joined #panfrost
<robclark>
maybe something about glamor is suboptimal compared to gl compositor? You could compare, for ex, glmark2 with wayland vs x11
<PaulFertser>
I tried doing perf record for both es2gears runs and the results were pretty much the same afaict.
<PaulFertser>
Yes, glmark2 gives extremely different results too, will show full logs a bit later. I suspect something is wrong with my Xorg config but it's all default Debian and moreover I'd like to understand where the difference might come from.
<rasterman>
realistically you will not measure anything useful between the 2
<rasterman>
99% of your pipeline is either entirely in compositor code or in client code
<rasterman>
the code is essentially the same
<rasterman>
you do 99% of the same and simple the path to request a buffer swap is marginally different
<rasterman>
both will send a request over a unix socket
<rasterman>
ther are no copies going down any pipes
<rasterman>
its "please take buffer X and swap it please"
<rasterman>
on the other side from the client (x+compositor vs wayland compositor) it's a bit different
<rasterman>
there is an extra bounce through the xorg server on the x side
<rasterman>
ie xserver implements the swap then sends unix socket msgs to compositor (damage events) ...
<rasterman>
well indirect == rendering of an app goes to some buffer and is stored there
<rasterman>
then a compositor takes over and that buffer gets displayed in some way by the compositor
<rasterman>
it may just blast it to the screen
<rasterman>
it may wrap it around a 3d spinning bunny rabbit
<rasterman>
it may fade it in and out and zoom it in and out
<rasterman>
add dropshadows or whatever it likes
<rasterman>
this is simply a choice of what the compositor wants to do display-wise to give the user some kind fo experience
<rasterman>
wtf is up with my rockpro64...
<PaulFertser>
And without compositor with direct rendering isn't it supposed to just blast it on screen right away?
<rasterman>
oh dang
<PaulFertser>
My Mesa isn't the latest, it's what Debian stable ships, I can compile HEAD if needed.
<rasterman>
thats what
Cyrinux947 has quit []
<PaulFertser>
I understand Xorg is dead etc. But I like my xmonad with xmobar, I like synaptics touchpad driver (libinput doesn't have the options I need), I like setxkbmap working right away...
<rasterman>
thats a problem then
<rasterman>
no compositor
<rasterman>
and wm and compositor are separate
Cyrinux947 has joined #panfrost
<PaulFertser>
So if I just add xcompmgr to .xinitrc then it somehow improves glmark2 automagically?
<rasterman>
that will have a likely worse pipeline as it'll use xrender to composite
<rasterman>
i can go on about why ... but no.. that wnt really help
<rasterman>
you need a gl based compositor
<rasterman>
you probabkly need it to indirect just the client window and nothing more - not the frame + border a wm might add
<PaulFertser>
What would be an example of such a compositor?
<rasterman>
there was once one
<rasterman>
i dont remember the name
<rasterman>
glcompmgr?
<rasterman>
i didnt pay much attention as my wm is a compositor and thats all i cared about
<rasterman>
and it does things in a way to allow for optimal pipelines
<rasterman>
gimme a bit
<rasterman>
i'm collecting benchmarks
<rasterman>
also after some updates trying to get xorg + panfrost to work again...
<rasterman>
grrr X .. why u so blank?
<PaulFertser>
It used to show that cool background by default. And supported Ctrl-Alt-Backspace...