This doesn't address the problem. First, the threads need to refer
to *different* graphics contexts. Second, the API requires that these
contexts be identified by some thread-specific mechanism available to
the graphics library, not by explicit stack pointers in the application
- whether that mechanism is private mappings or tarot cards matters not,
so long as it's extremely fast.
I assumed these points were both clear from my initial post, and not
really occasion for a rant about how "unstable and unmaintainable" IRIX
is, but whatever - so long as in the end Linux allows apps to issue
vertices at least as fast as other OSes on the same hardware.
Jon Leech
SGI
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/