> By making transfers context-private and non-shareable, it becomes > possible for a driver to implement interleaved drawing and dma-uploads > within a single command buffer.
While we do this, how about removing transfer map and unmap functions and making the create and destroy functions do mapping and unmapping? Since the transfer contents are flushed on destroy, anything other than calling map just after create and unmap just before destroy does not offer any benefit, so we may as well merge the functionality. Another option would be to flush on unmap and let transfer objects be permanent, but I think this would complicate both state trackers and drivers for a very dubious performance improvement. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
