Re: [Dri-devel] issues/goals for improved texture memory management

2002-10-07 Thread Ian Romanick
Here is the texmem patch that I talked about at last week's (sorry for the massive delay!) IRC meeting. There's a patch file and a couple new files. Also, mga/mgatexcnv.c should be removed. I'm not sure how to specify removing a file in a patch. :) In any case, I'm primarilly sending this out

Re: [Dri-devel] issues/goals for improved texture memory management

2002-10-03 Thread Benjamin Herrenschmidt
On Mac OS X (from 10.1 on, I believe), the OS can map any memory page into the AGP aperture at any time. The idea behind A_cs is that people malloc space for a texture, specify GL_UNPACK_CLIENT_STORAGE_APPLE to glPixelStorei, then call glTexImage?D with their pointer. The GL driver then keeps

Re: [Dri-devel] issues/goals for improved texture memory management

2002-10-02 Thread Ian Romanick
On Mon, Sep 30, 2002 at 05:07:39PM -0600, Brian Paul wrote: This was a topic on today's IRC session. Here's a very rough list of issues and goals to consider. After we get a good list we can move onto implementation proposals. If we're really going to do this, let's be sure we do it right.

Re: [Dri-devel] issues/goals for improved texture memory management

2002-10-02 Thread Jens Owen
Ian Romanick wrote: Really there are 3 places the texture data can be duplicated: in the app, in libGL, and on-card / AGP. This can either be done by exposing some sort of allocate AGP memory extension or with APPLE_client_storage and dynamic AGP remapping. I've done a cursory look at

Re: [Dri-devel] issues/goals for improved texture memory management

2002-10-02 Thread Ian Romanick
On Wed, Oct 02, 2002 at 04:35:16PM -0600, Jens Owen wrote: Ian Romanick wrote: Really there are 3 places the texture data can be duplicated: in the app, in libGL, and on-card / AGP. This can either be done by exposing some sort of allocate AGP memory extension or with

[Dri-devel] issues/goals for improved texture memory management

2002-09-30 Thread Brian Paul
This was a topic on today's IRC session. Here's a very rough list of issues and goals to consider. After we get a good list we can move onto implementation proposals. If we're really going to do this, let's be sure we do it right. Please contribute comments, new issues, etc. -Brian 1.