Announcement

Collapse
No announcement yet.

Trinity APU memory layout?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    According to Anandtech, pinned memory is bad (one extra memcpy), and with Trinity (IOMMUv2) is no longer needed:

    IOMMU v2 is also supported by Trinity, giving supported discrete GPUs (e.g. Tahiti) access to the CPU's virtual memory. In Llano, you used to take data from disk, copy it to memory, then copy it from the CPU's address space to pinned memory that's accessible by the GPU, then the GPU gets it and brings it into its frame buffer. By having access to the CPU's virtual address space now the data goes from disk, to memory, then directly to the GPU's memory—you skip that intermediate mem to mem copy. Eventually we'll get to the point where there's truly one unified address space, but steps like these are what will get us there.
    http://www.anandtech.com/show/5831/a...m-a-new-hope/2

    Comment

    Working...
    X