Roland Scheidegger wrote:
Keith Whitwell wrote:
Right now, I'm primarily concerned with unified memory chipsets, like
i915 and via. This memory manager would be suitable for managing the
AGP memory on non-unified chipsets, but a different implementation
would be needed for the on-card video
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benjamin Herrenschmidt wrote:
- Caching issues. On a lot of chipsets, AGP memory must be mapped
non-cacheable. This isn't trivial on all architectures and it's not
always feasible to do with userland buffers. That means that either the
cache must
There must be some way to deal with all this sanely on PPC. Apple has a
number of OpenGL extensions for making user memory directly accessable
to the graphics engine. Perhaps their specs can provide some clues as
to how they do it?
This follows on from the previous post to discuss an implementation of
the memory manager for managing only AGP memory.
Right now, I'm primarily concerned with unified memory chipsets, like
i915 and via. This memory manager would be suitable for managing the
AGP memory on non-unified chipsets,
Keith Whitwell wrote:
1) I think this is the first solution for memory management that I can
imagine implementing. Also it's one which gives reasonable
performance when data is being evicted from the GART.
This sounds a little trite reading it back.
This a function of two things,
On Sun, 2006-01-08 at 18:17 +, Keith Whitwell wrote:
In the past there has been talk about mapping user memory into the GTT
aperture as a mechanism to avoid copy-based uploading. What I'm
proposing is that this type of mapping becomes the only or at least
primary way of getting data and
Benjamin Herrenschmidt wrote:
On Sun, 2006-01-08 at 18:17 +, Keith Whitwell wrote:
In the past there has been talk about mapping user memory into the GTT
aperture as a mechanism to avoid copy-based uploading. What I'm
proposing is that this type of mapping becomes the only or at least
On Sun, 2006-01-08 at 22:55 +, Keith Whitwell wrote:
Yes, this I think is addressed by the Map/Unmap semantics from ARB_vbo and
the
additional constraints I included in the design, ie that the only time the
buffer contents are meant to be available as user memory is when they are
Indeed. I think that taking the API from ARB_vbo makes these different
implementations entirely possible. The implementation I am interested in right
now is the AGP one, but don't take that to imply that other implementations and
backends are excluded.
I've tried to provide exactly the
Keith Whitwell wrote:
Right now, I'm primarily concerned with unified memory chipsets, like
i915 and via. This memory manager would be suitable for managing the
AGP memory on non-unified chipsets, but a different implementation
would be needed for the on-card video ram, based more on dma and
10 matches
Mail list logo
