> > I've attempted some rather pathetic rate-adaption to make everything slow > down when the FIFO gets full. It utterly murders performance but it did > prevent the lockup from occurring. I modified ADVANCE_RING to take a > parameter containing a Wild-Ass-Guess of how many commands were being > added, then to call COMMIT_RING if it got over the maximum. COMMIT_RING > then read the number of free FIFO slots and adjusted the maximum up or down > depending on how well we were doing, and started to hang around for a bit > if things were getting full.
This seems confused (or maybe it's me?). The COMMIT_RING is the only thing in common use in the 3d driver that should write to the fifo, I think. Calling COMMIT_RING more often means that more fifo entries are getting used? Keith _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
