search for: 270ms

...se you have access to information on more realistic >> timeouts? I'd like to improve all the potential 2s timeout values >> across the driver in general, to avoid things hanging for a long time >> when the GPU craps itself :) > > The longest values I have ever seen are ~270ms (only during driver > initialization, and at low clock speeds), but anyway this should never > ever timeout. If it does, then we will have bigger issues than 2 > second timeouts. :) Indeed it shouldn't, but when things get horribly messed up (as happens occasionally :P) it's annoyi...

On 3 September 2015 at 16:42, Alexandre Courbot <acourbot at nvidia.com> wrote: > Allow clients to manually flush and invalidate L2. This will be useful > for Tegra systems for which we want to write instmem using the CPU. > > Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> > --- > drm/nouveau/include/nvkm/subdev/ltc.h | 1 + >

...INFO -- Rendering of website </tmp/testsite> finished real 0m0.269s user 0m0.191s sys 0m0.070s erebus:~/work/webgen/devel thomasleitner$ As you can see, nothing is written the second time because nothing has changed! Also notice the overall execution time of around 270ms. Estimated 180ms - 220ms are used for loading Rubygems and dependencies. webgen 0.4.2 needs about twice the time! That''s all for now! -- Thomas

...t I'd like to see if I can get feedback on two questions: (1) Through the current release (v4.0), Silverlight introduces a surprising amount of latency when playing and recording audio. The time from when I submit a sound to be played until I record that sound coming back ranges from 230ms to 270ms, depending on the machine. This is roughly a 12-frame delay, and is obviously much larger than the 2-frame latency that Jean-Marc assumed when he was coding up the Speex AEC. One possible way of compensating for this would be to increase the tail (to make room for ~350ms worth of sound), but I ha...