Re: [Mesa3d-dev] gallium cached bufmgr busy change

2010-03-29 Thread José Fonseca
On Tue, 2010-03-23 at 02:07 -0700, Dave Airlie wrote: On Mon, Mar 8, 2010 at 5:51 PM, Jose Fonseca jfons...@vmware.com wrote: Dave, I don't oppose this new method -- it shouldn't be necessary to add fencing just to use pb_cache --, but this method adds a new way of doing the same

Re: [Mesa3d-dev] gallium cached bufmgr busy change

2010-03-23 Thread Dave Airlie
On Mon, Mar 8, 2010 at 5:51 PM, Jose Fonseca jfons...@vmware.com wrote: Dave, I don't oppose this new method -- it shouldn't be necessary to add fencing just to use pb_cache --,  but this method adds a new way of doing the same thing. Does the underlying buffer support

Re: [Mesa3d-dev] gallium cached bufmgr busy change

2010-03-23 Thread Dave Airlie
On Tue, Mar 23, 2010 at 11:41 PM, Luca Barbieri luca.barbi...@gmail.com wrote: Do Radeons have a CP command to write an arbitrary value to some place in memory? If so, you may want to use that to implement userspace-accessible fencing in the obvious way and then use the fenced bufmgr, which

Re: [Mesa3d-dev] gallium cached bufmgr busy change

2010-03-09 Thread Luca Barbieri
We can do this optimisation with busy as well. As long as you add things to the busy list at the end, and stop testing after the first busy call. At least for a single linear GPU context, which is all I expect this code will ever be handling. Wouldn't this just end up reinventing the fenced

Re: [Mesa3d-dev] gallium cached bufmgr busy change

2010-03-08 Thread Dave Airlie
On Tue, Mar 9, 2010 at 11:30 AM, Luca Barbieri luca.barbi...@gmail.com wrote: The fencing solution isn't near as efficent from what I can see, as it is designed around fences not buffer busy, I'll see if I can give it a try, but I suspect it look and smell like a hack. The problem I see is

Re: [Mesa3d-dev] gallium cached bufmgr busy change

2010-03-07 Thread Luca Barbieri
I think you are supposed to do this using the fenced bufmgr over cached along with a (ideally userspace) fencing mechanism. If you can implement pb_busy, you should be able to implement fence_signalled in exactly the same way (making the fence handle a pointer to buffers should work for this

Re: [Mesa3d-dev] gallium cached bufmgr busy change

2010-03-07 Thread Dave Airlie
On Sun, Mar 7, 2010 at 9:44 PM, Luca Barbieri luca.barbi...@gmail.com wrote: I think you are supposed to do this using the fenced bufmgr over cached along with a (ideally userspace) fencing mechanism. If you can implement pb_busy, you should be able to implement fence_signalled in exactly the

Re: [Mesa3d-dev] gallium cached bufmgr busy change

2010-03-07 Thread Jose Fonseca
: Dave Airlie [airl...@gmail.com] Sent: Sunday, March 07, 2010 20:36 To: Luca Barbieri Cc: mesa Subject: Re: [Mesa3d-dev] gallium cached bufmgr busy change On Sun, Mar 7, 2010 at 9:44 PM, Luca Barbieri luca.barbi...@gmail.com wrote: I think you are supposed to do this using the fenced bufmgr over

[Mesa3d-dev] gallium cached bufmgr busy change

2010-03-06 Thread Dave Airlie
I've been playing with strategies to get r300 buffer management a bit more efficient, I've reworked the r300g screen/winsys and create a pb_bufmgr compliant buffer class, and stacked the cached buffer manager on top of it. Now I've hit a problem in that we expose buffer busy state, but the