Page 1 of 5 123 ... LastLast
Results 1 to 10 of 45

Thread: Radeon Memory Boost: Up To 50%+ Better Performance

  1. #1
    Join Date
    Jan 2007
    Posts
    14,324

    Default Radeon Memory Boost: Up To 50%+ Better Performance

    Phoronix: Radeon Memory Boost: Up To 50%+ Better Performance

    Marek Olk published a set of Radeon memory management improvements today for the open-source AMD Linux graphics driver that can offer performance improvements...

    http://www.phoronix.com/vr.php?view=MTYxMzM

  2. #2
    Join Date
    Jul 2008
    Location
    Germany
    Posts
    621

    Default

    Would be nice to see some Benchmarks, especially Source based Games.

  3. #3
    Join Date
    Jan 2007
    Posts
    418

    Default

    But what about r300? My poor T42 feels left out

  4. #4
    Join Date
    Mar 2011
    Posts
    374

    Default

    Will this also benefit 2GB cards? I heard that the FOSS driver copies a lot of data back and forth between video RAM and system RAM, does this (or one of the future patches) reduce that or is it really only for limited cards?

  5. #5
    Join Date
    Nov 2010
    Posts
    332

    Default

    This definitely calls for a new set of benchmarks for a wide range of graphic cards.

  6. #6
    Join Date
    Dec 2009
    Location
    Italy
    Posts
    174

    Default

    Code:
    /* This function is based on the current VRAM usage.
    	 *
    	 * - If all of VRAM is free, allow relocating the number of bytes that
    	 *   is equal to 1/4 of the size of VRAM for this IB.
    
    	 * - If more than one half of VRAM is occupied, only allow relocating
    	 *   1 MB of data for this IB.
    	 *
    	 * - From 0 to one half of used VRAM, the threshold decreases
    	 *   linearly.
    	 *         __________________
    	 * 1/4 of -|\               |
    	 * VRAM    | \              |
    	 *         |  \             |
    	 *         |   \            |
    	 *         |    \           |
    	 *         |     \          |
    	 *         |      \         |
    	 *         |       \________|1 MB
    	 *         |----------------|
    	 *    VRAM 0 %             100 %
    	 *         used            used
    	 *
    	 * Note: It's a threshold, not a limit. The threshold must be crossed
    	 * for buffer relocations to stop, so any buffer of an arbitrary size
    	 * can be moved as long as the threshold isn't crossed before
    	 * the relocation takes place. We don't want to disable buffer
    	 * relocations completely.
    	 *
    	 * The idea is that buffers should be placed in VRAM at creation time
    	 * and TTM should only do a minimum number of relocations during
    	 * command submission. In practice, you need to submit at least
    	 * a dozen IBs to move all buffers to VRAM if they are in GTT.
    	 *
    	 * Also, things can get pretty crazy under memory pressure and actual
    	 * VRAM usage can change a lot, so playing safe even at 50% does
    	 * consistently increase performance.
    	 */
    Wow marek's an artist too! :P

  7. #7
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    904

    Default

    Quote Originally Posted by kbios View Post
    Code:
    /* This function is based on the current VRAM usage.
    	 *
    	 * - If all of VRAM is free, allow relocating the number of bytes that
    	 *   is equal to 1/4 of the size of VRAM for this IB.
    
    	 * - If more than one half of VRAM is occupied, only allow relocating
    	 *   1 MB of data for this IB.
    	 *
    	 * - From 0 to one half of used VRAM, the threshold decreases
    	 *   linearly.
    	 *         __________________
    	 * 1/4 of -|\               |
    	 * VRAM    | \              |
    	 *         |  \             |
    	 *         |   \            |
    	 *         |    \           |
    	 *         |     \          |
    	 *         |      \         |
    	 *         |       \________|1 MB
    	 *         |----------------|
    	 *    VRAM 0 %             100 %
    	 *         used            used
    	 *
    	 * Note: It's a threshold, not a limit. The threshold must be crossed
    	 * for buffer relocations to stop, so any buffer of an arbitrary size
    	 * can be moved as long as the threshold isn't crossed before
    	 * the relocation takes place. We don't want to disable buffer
    	 * relocations completely.
    	 *
    	 * The idea is that buffers should be placed in VRAM at creation time
    	 * and TTM should only do a minimum number of relocations during
    	 * command submission. In practice, you need to submit at least
    	 * a dozen IBs to move all buffers to VRAM if they are in GTT.
    	 *
    	 * Also, things can get pretty crazy under memory pressure and actual
    	 * VRAM usage can change a lot, so playing safe even at 50% does
    	 * consistently increase performance.
    	 */
    Wow marek's an artist too! :P
    Not quite, but close:

    gnuplot> set term dumb

  8. #8

    Default

    Music to my ears

  9. #9
    Join Date
    Jan 2014
    Posts
    10

    Default

    Quote Originally Posted by oliver View Post
    But what about r300? My poor T42 feels left out
    The most recent r300 chip is almost 10 years old now. Might be time for an upgrade.

  10. #10
    Join Date
    Sep 2008
    Location
    Vilnius, Lithuania
    Posts
    2,518

    Default

    Interesting, I wonder if this affects APUs as well. A super low-end AMD netbook I maintain might like these changes once I switch to the open drivers (which is as soon as Gentoo stabilises 3.13, which might be in a week or in a month).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •