Comment=
# 8
on bug 75719<=
/a>
from Thomas Hellstr=C3=B6m
There's really nothing in this commit that should affect anyth=
ing but metadata,
and if anything, CPU usage should've decreased.
So if CPU usage is drastically increased by this commit (or rather this mer=
ge),
IMHO that points to a bug somewhere else, but triggered by this merge; poss=
ibly
in radeon / TTM caching setup or in the x86 PAT memory region tracking code.
In any case, I'm on out-of-office this week and can't look at this before n=
ext
week, but meantime it would be helpful if you could perform a couple of
additional checks:
1) Try to find out which of the commits in the merge that causes this. If t=
hat
turns out to be hard, could you change all occurencies of VM_PFNMAP in
ttm_bo_mmap() (ttm_bo_vm.c) to VM_MIXEDMAP and check if that fixes the prob=
lem
you are seeing?
2) If you're familiar with oprofile, it would be very helpful to see a prof=
ile
of a "good" and a "bad" run, including kernel symbols.
Thanks,
/Thomas