Bug 796

Summary: Add DMX to X.Org
Product: xorg Reporter: Kevin E. Martin <kem>
Component: Server/GeneralAssignee: Kevin E. Martin <kem>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: high CC: ajax, roland.mainz
Version: git   
Hardware: x86 (IA32)   
OS: All   
URL: http://dmx.sourceforge.net/
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Patch to add DMX support to X.Org
none
Tar file of newly added files for DMX support none

Description Kevin E. Martin 2004-06-22 18:34:43 UTC
Distributed Multihead X (DMX) is a system for distributing the X server across
multiple machines.  For detailed info on the DMX project, please see the URL
listed above.  We have developed the code over the past 2.5 years on SourceForge
and is now ready to be moved upstream.
Comment 1 Kevin E. Martin 2004-06-22 18:35:24 UTC
After review, I will commit this to the X.Org CVS tree.
Comment 2 Kevin E. Martin 2004-06-22 18:37:44 UTC
Created attachment 411 [details] [review]
Patch to add DMX support to X.Org
Comment 3 Kevin E. Martin 2004-06-22 18:38:48 UTC
Created attachment 412 [details]
Tar file of newly added files for DMX support
Comment 4 Adam Jackson 2004-06-22 19:25:51 UTC
kevin, does this address bug 578 at all?  specifically alan's point about mixing
Mesa and Xinerama.

also, does the glxproxy work to accelerate indirect rendering even for normal
servers?
Comment 5 Kevin E. Martin 2004-06-23 08:28:43 UTC
(In reply to comment #4)
> kevin, does this address bug 578 at all?  specifically alan's point about mixing
> Mesa and Xinerama.

GLX Proxy acts as a proxy server and distributes GLX protocol to multiple
back-end servers to which DMX is attached, so when Xinerama is used, I think it
will address the OpenGL with Xinerama issue.  However, Cromium is the best solution.

> also, does the glxproxy work to accelerate indirect rendering even for normal
> servers?

No, it's just a proxy server, so it just takes advantage of whatever indirect
rendering is available.  If the back-end server already has accelerated indirect
rendering, then GLX Proxy will take advantage of it, but if it isn't
accelerated, then GLX Proxy won't be either.
Comment 6 Roland Mainz 2004-06-23 16:40:45 UTC
Comment on attachment 411 [details] [review]
Patch to add DMX support to X.Org

I see one nit with the patch - is it wise to use the cpp symbol |DMX| in such a
large codebase ?
IMHO something longer (e.g. more than three letters) may be better...
Comment 7 Kevin E. Martin 2004-06-23 21:46:12 UTC
(In reply to comment #6)
> (From update of attachment 411 [details] [review])
> I see one nit with the patch - is it wise to use the cpp symbol |DMX| in such a
> large codebase ?
> IMHO something longer (e.g. more than three letters) may be better...

The DMX cpp symbol is only used in the xdyinfo patch, and we were following the
convention that others used (e.g., MITSHM, XKB, XF86VIDMODE, etc.).  If there is
a strong feeling against using DMX cpp symbol in xdpyinfo, we can certainly
change it.
Comment 8 Roland Mainz 2004-06-23 21:51:14 UTC
kem@freedesktop.org wrote:
> (In reply to comment #6)
> > (From update of attachment 411 [details] [review])
> > I see one nit with the patch - is it wise to use the cpp symbol |DMX| in 
> > such a large codebase ?
> > IMHO something longer (e.g. more than three letters) may be better...
>
> The DMX cpp symbol is only used in the xdyinfo patch, and we were following 
> the convention that others used (e.g., MITSHM, XKB, XF86VIDMODE, etc.).  If 
> there is a strong feeling against using DMX cpp symbol in xdpyinfo, we can 
> certainly change it.

If the |DMX| symbol is only used in xdpyinfo (which is itself a tiny
application) then it is OK... I only feared - without checking that in detail -
that this symbol is used all over the tree.
Sorry for the false alarm... I should have this checked twice before running
around and screaming... :)
Comment 9 Kevin E. Martin 2004-06-30 13:15:21 UTC
Support for DMX checked-in.  Thank you to all who reviewed the patches.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.