On Wed, 28 Jan 2009 11:30:53 + (GMT)
Dave Airlie wrote:
> Good point, the attached fixes that.
it looks more proper!
> Yes it should be fine, write combining shouldn't re-order,
> and its been write combined using an mtrr for years.
WC has weak-ordering.
For FrameBuffer data, correctness isn
oh I filled bugzilla.kernel.org right now ...
On Wed, 28 Jan 2009 09:31:32 + (GMT)
Dave Airlie wrote:
> Does the attached patch help?
I also think so once,
but it will be bad with cant_use_aperture AGP.
my patch attached to bugzilla.
BTW using Write-Combining for ring-buffer is safe?
I afra
Hi, I encountered huge-grown memory leak in recently update and investigated by
valgrind.
The leak found in _tnl_UpdateFixedFunctionProgram that was 'state_key key' keep
created always.
==5636== 1,319,960 bytes in 32,999 blocks are definitely lost in loss record 63
of 65
==5636==at 0x4005B0