Page 1 of 4 123 ... LastLast
Results 1 to 10 of 38

Thread: Mesa Mega Driver Patches Published

  1. #1
    Join Date
    Jan 2007
    Posts
    13,395

    Default Mesa Mega Driver Patches Published

    Phoronix: Mesa Mega Driver Patches Published

    Eric Anholt of Intel has published his initial patches for implementing the "mega drivers" concept within Mesa...

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

  2. #2
    Join Date
    Oct 2009
    Location
    .ca
    Posts
    392

    Default

    Doesn't seem to make too much sense from a technical point of view. Anybody has an idea about the politics side?

  3. #3
    Join Date
    Jan 2011
    Posts
    1,287

    Default

    Quote Originally Posted by not.sure View Post
    Doesn't seem to make too much sense from a technical point of view. Anybody has an idea about the politics side?
    On politics, if forced (i.e., if it's not just a build time option) means you need to rebuild the whole mesa to use any driver that is not upstream.
    On tech, I think it has some security/stability relevance, since they don't need to make all the symbols public.

  4. #4
    Join Date
    Oct 2008
    Posts
    2,904

    Default

    Quote Originally Posted by not.sure View Post
    Doesn't seem to make too much sense from a technical point of view. Anybody has an idea about the politics side?
    Hiding all the symbols is a huge win on the technical side - although possibly it could be done in another way, i'm not sure about that.

  5. #5
    Join Date
    Jul 2013
    Posts
    223

    Default

    Quote Originally Posted by not.sure View Post
    Doesn't seem to make too much sense from a technical point of view. Anybody has an idea about the politics side?
    um...

    and is noting about a 2.61% performance increase
    It reduces some CPU load due to moving some calls to internal instead of across linked libraries. Also, once Gallium gets added to the mix, it will create a single binary that's about 1/6 the size of the current Mesa package (if you include ALL drivers, like some distros do)

  6. #6
    Join Date
    Dec 2010
    Location
    MA, USA
    Posts
    1,100

    Default

    Michael, any chances on benchmarking this driver against the ones it merges?

  7. #7
    Join Date
    Nov 2008
    Posts
    142

    Default I hope this stays optional.

    Mega binaries are not a good practice and the performance benefits seem negligible. Modularization is harder but almost always the better approach.

  8. #8
    Join Date
    Jul 2007
    Posts
    428

    Default I really hope this is a configurable option

    Quote Originally Posted by phoronix View Post
    Eric Anholt of Intel has published his initial patches for implementing the "mega drivers" concept within Mesa...
    This is exactly the kind of thing I don't need when trying to perform a "git bisect".

  9. #9
    Join Date
    Dec 2011
    Posts
    1,931

    Default Is this even a good idea?

    Big monolithic things are usually bad.

    Isn't there any alternative ways do accomplish similar benefits without the drawbacks?

    I don't think anyone else (Apple or Microsoft, etc) would use this solution.

  10. #10
    Join Date
    Jan 2013
    Posts
    906

    Default

    I know the much easier and future proof approach.
    Gallium.

Posting Permissions

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