Re: [PATCH 1/3] drm/vmwgfx: Don't use memory accounting for kernel-side fence objects

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2 December 2014 at 21:59, Thomas Hellstrom <thellstrom@xxxxxxxxxx> wrote:
> Kernel side fence objects are used when unbinding resources and may thus be
> created as part of a memory reclaim operation. This might trigger recursive
> memory reclaims and result in the kernel running out of stack space.
>
> So a simple way out is to avoid accounting of these fence objects.
> In principle this is OK since while user-space can trigger the creation of
> such objects, it can't really hold on to them. However, their lifetime is
> quite long, so some form of accounting should perhaps be implemented in the
> future.
>
> Fixes kernel crashes when running, for example viewperf11 ensight-04 test 3
> with low system memory settings.

are these 3 intended for fixes? can you send me a git pull for them
soon, so they don't miss Linus release.

Dave.
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]