Theo Buehler <t...@theobuehler.org> wrote:
> On Sat, Feb 27, 2021 at 12:21:35AM +1100, Jonathan Gray wrote:
> > Bring in a change which was backported to Mesa 20.1 but not 20.0.
> > This is for inteldrm with >= gen8/broadwell hardware.
> > /var/log/Xorg.0.log with 'DRI driver: iris' and 'xdriinfo' will
> > show 'Screen 0: iris' if you are using the iris driver.
>
> This seems to help a lot on my x280 where xdriinfo prints Screen 0: iris.
>
> inteldrm0 at pci0 dev 2 function 0 "Intel UHD Graphics 620" rev 0x07
> drm0 at inteldrm0
> inteldrm0: msi, KABYLAKE, gen 9
> inteldrm0: 1920x1080, 32bpp
>
> I hadn't paid attention to it previously, but as observed yesterday
> after a few hours of uptime, Xorg would already use way above 100M
> and grow steadily.
>
> Running with this patch overnight I'm at the below which apart from the
> TIME column looks pretty much like right after startup.
>
> PID USERNAME PRI NICE SIZE RES STATE WAIT TIME CPU COMMAND
> 24637 _x11 2 0 35M 65M sleep/1 poll 1:29 0.10% Xorg
> 20308 root 2 0 2464K 1284K idle netio 0:00 0.00% Xorg
35MB of memory is too large to expose amap leakage, since most of the amaps
are associated with single pages. The X server does some very large
allocations,
and thus SIZE will not show these very well.
To see the problem, It is better to look at "UVM amap" in "vmstat -m"
UVM amap 32835 1690K 2636K 78644K 26812908 0
16,32,64,128,256,512,1024,4096,8192
^^^^ this number is way too big, it should be 500 to 2000 ish.
