18 um 17:30 schrieb Jean-Marc Valin:
>> Hi Christian,
>>
>> Is there a way to turn off these huge pages at boot-time/run-time?
>
> Only at compile time by not setting CONFIG_TRANSPARENT_HUGEPAGE.
>
> Alternatively you can avoid enabling CONFIG_SWIOTLB which
On 04/11/2018 05:37 AM, Christian König wrote:
>> With your patches my EPYC box is unusable with 4.15++ kernels.
>> The whole Desktop is acting weird. This one is using
>> an Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] GPU.
>>
>> Box is 2 * EPYC 7281 with 128 GB ECC RAM
>>
>> Also a 14C Xeon
On 04/09/2018 05:42 AM, Christian König wrote:
> Backporting all the detection logic is to invasive, but you could just
> go into drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c and forcefull use the
> other code path.
>
> Just look out for "#ifdef CONFIG_SWIOTLB" checks and disable those.
Do you mean ju
uot;offending"
patch reverted. Is that safe to run or are there possible bad
interactions with other changes.
Cheers,
Jean-Marc
On 04/06/2018 01:20 PM, Christian König wrote:
> Am 06.04.2018 um 18:42 schrieb Jean-Marc Valin:
>> Hi Christian,
>>
>> On 04/09/2018 07:48 A
tially somebody needs to
> figure out why firefox and/or the user space stack is doing this
> constant allocation/freeing of memory.
>
> There is also a bug tracker on bugs.kernel.org about this, but I can't
> find it any more of hand.
>
> Regards,
> Christian.
>
>
Hi Christian,
On 04/09/2018 07:48 AM, Christian König wrote:
> Am 06.04.2018 um 17:30 schrieb Jean-Marc Valin:
>> Hi Christian,
>>
>> Is there a way to turn off these huge pages at boot-time/run-time?
>
> Only at compile time by not setting CONFIG_TRANSPARENT_HUGEPAGE.
Hi,
I noticed a serious graphics performance regression between 4.14 and
4.15. It is most noticeable with Firefox (tried FF57 through FF60) and
causes scrolling to be really choppy/sluggish. I've confirmed that the
problem is also there on 4.16, while 4.13 works fine.
After a bisection, I've narr
