search for: sets_

...The working sets are initially marked as dirty. - User space tells which working sets are referenced by each work submission. Kernel locks these working sets, pins all buffers in dirty working sets, and resets the dirty bits. After kicking off work, kernel stores the fence to the _working sets_, and then releases the locks (if an implicit default working set is used, then this would be roughly equivalent to storing a fence to channel vm that tells "this is the last hw operation that might have touched buffers in this address space"). - If swapping doesn't happen, then...

...as dirty. > > - User space tells which working sets are referenced by each work submission. > > Kernel locks these working sets, pins all buffers in dirty working sets, and > > resets the dirty bits. After kicking off work, kernel stores the fence to > > the _working sets_, and then releases the locks (if an implicit default > > working set is used, then this would be roughly equivalent to storing a fence > > to channel vm that tells "this is the last hw operation that might have > > touched buffers in this address space"). > >...

...; initially marked as dirty. > - User space tells which working sets are referenced by each work submission. > Kernel locks these working sets, pins all buffers in dirty working sets, and > resets the dirty bits. After kicking off work, kernel stores the fence to > the _working sets_, and then releases the locks (if an implicit default > working set is used, then this would be roughly equivalent to storing a fence > to channel vm that tells "this is the last hw operation that might have > touched buffers in this address space"). > - If swapping doesn...

...> - User space tells which working sets are referenced by each work submission. > > > Kernel locks these working sets, pins all buffers in dirty working sets, and > > > resets the dirty bits. After kicking off work, kernel stores the fence to > > > the _working sets_, and then releases the locks (if an implicit default > > > working set is used, then this would be roughly equivalent to storing a fence > > > to channel vm that tells "this is the last hw operation that might have > > > touched buffers in this address space&qu...

...working sets are referenced by each work > submission. > > > > Kernel locks these working sets, pins all buffers in dirty working > sets, and > > > > resets the dirty bits. After kicking off work, kernel stores the > fence to > > > > the _working sets_, and then releases the locks (if an implicit > default > > > > working set is used, then this would be roughly equivalent to > storing a fence > > > > to channel vm that tells "this is the last hw operation that might > have > > > > touched bu...

Hi guys, I'd like to start a new thread about explicit fence synchronization. This time with a Nouveau twist. :-) First, let me define what I understand by implicit/explicit sync: Implicit synchronization * Fences are attached to buffers * Kernel manages fences automatically based on buffer read/write access Explicit synchronization * Fences are passed around independently * Kernel takes