Page 1 of 7 123 ... LastLast
Results 1 to 10 of 65

Thread: Gallium3D / LLVMpipe With LLVM 2.8

  1. #1
    Join Date
    Jan 2007
    Posts
    15,388

    Default Gallium3D / LLVMpipe With LLVM 2.8

    Phoronix: Gallium3D / LLVMpipe With LLVM 2.8

    While LLVM 2.8 was just released, we have been curious to see how the latest Low-Level Virtual Machine compiler code affects the performance of the LLVMpipe driver. This is the Gallium3D graphics driver that lives in Mesa and leverages the unique modular LLVM compiler to efficiently handle processing the graphics rendering workload on a modern CPU as a much faster alternative to that of their legacy software rasterizer. To see how much of a performance impact - for better or worse - that LLVM 2.8 has on this open-source software driver we tested it when being built with LLVM 2.6, 2.7, and the 2.8 SVN code.

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

  2. #2

    Default

    is still too slow for most computers
    Fixed for you

  3. #3
    Join Date
    Jul 2009
    Posts
    260

    Default

    i thought you disabled assertions?!?
    the pic says "optimised build WITH assertions"
    and you took a build from september?

  4. #4
    Join Date
    Oct 2009
    Posts
    343

    Default

    good its improving, but still no chance to swap from fglrx

  5. #5
    Join Date
    Jun 2009
    Posts
    2,932

    Default

    Quote Originally Posted by NomadDemon View Post
    good its improving, but still no chance to swap from fglrx
    You're expecting a CPU-based rasteriser to beat an optimized binary hardware driver?

  6. #6
    Join Date
    Oct 2009
    Posts
    343

    Default

    cpu you say? so what its for? mesa is hardware... galium should be "new mesa" so wheres the problem?

  7. #7
    Join Date
    Jun 2009
    Posts
    2,932

    Default

    Why don't you read the article?

  8. #8
    Join Date
    Dec 2009
    Location
    Italy
    Posts
    176

    Default

    Is it only me or lately llvmpipe has been disabled in xorg-edgers? Since about a week, running LIBGL_DRIVERS_PATH="/usr/lib/dri/gallium" glxinfo|grep renderer outputs OpenGL renderer string: Gallium 0.4 on softpipe
    DRI experimental and Llvm are installed, of course.

  9. #9
    Join Date
    Oct 2009
    Posts
    343

    Default

    iam not native english, dont understand half of article, thats why i skip large part of it, more info i can get from comments, your language is easier

  10. #10
    Join Date
    Jun 2009
    Posts
    2,932

    Default

    Every sane GL library needs a software fallback for the case that the driver does not implement hardware acceleration for particular functionality. In that case, the CPU is used to perform such operations. It will be considerably slower, but at least it will render correctly, which is what the library is supposed to do.

    Mesa implements all of OpenGL in software, for such a case. The individual hardware drivers in Mesa then accelerate most of the things so you never need to run the software (CPU-based) path.

    Gallium3d has the same thing, and it's called softpipe. You can run OpenGL programs on that, but it's very slow.

    llvmpipe uses llvm (http://en.wikipedia.org/wiki/Llvm) and serves as a replacement for softpipe. Although everything is run on the CPU, it is much faster than softpipe, and can even offer acceptable performance for some simpler tasks.

    That is what this article is benchmarking.

Tags for this Thread

Posting Permissions

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