Sponsored Content
Full Discussion: Airlines industry
Special Forums News, Links, Events and Announcements Airlines industry Post 302968143 by jgt on Friday 4th of March 2016 08:38:56 AM
Old 03-04-2016
Look at the number of threads in the Operating System section.
Solaris and RedHat have by far the most threads. Of course that could have several meanings: either there are significantly more of these installations, or the people using these systems are less knowledgeable.Smilie
 

We Also Found This Discussion For You

1. What is on Your Mind?

3D screens in surgical industry

I just had this odd idea that may even have some future. The advent of 3D screens for the mass market might prove useful for the healthcare industry, while in surgical practices they rely on medical imagery more and more often. Perhaps the introduction of 3D screens will give the illusion of depth... (4 Replies)
Discussion started by: figaro
4 Replies
XInitThreads(3) 						  XLIB FUNCTIONS						   XInitThreads(3)

NAME
XInitThreads, XLockDisplay, XUnlockDisplay - multi-threading support SYNTAX
Status XInitThreads(void); void XLockDisplay(Display *display); void XUnlockDisplay(Display *display); ARGUMENTS
display Specifies the connection to the X server. DESCRIPTION
The XInitThreads function initializes Xlib support for concurrent threads. This function must be the first Xlib function a multi-threaded program calls, and it must complete before any other Xlib call is made. This function returns a nonzero status if initialization was suc- cessful; otherwise, it returns zero. On systems that do not support threads, this function always returns zero. It is only necessary to call this function if multiple threads might use Xlib concurrently. If all calls to Xlib functions are protected by some other access mechanism (for example, a mutual exclusion lock in a toolkit or through explicit client programming), Xlib thread ini- tialization is not required. It is recommended that single-threaded programs not call this function. The XLockDisplay function locks out all other threads from using the specified display. Other threads attempting to use the display will block until the display is unlocked by this thread. Nested calls to XLockDisplay work correctly; the display will not actually be unlocked until XUnlockDisplay has been called the same number of times as XLockDisplay. This function has no effect unless Xlib was successfully initialized for threads using XInitThreads. The XUnlockDisplay function allows other threads to use the specified display again. Any threads that have blocked on the display are allowed to continue. Nested locking works correctly; if XLockDisplay has been called multiple times by a thread, then XUnlockDisplay must be called an equal number of times before the display is actually unlocked. This function has no effect unless Xlib was successfully ini- tialized for threads using XInitThreads. SEE ALSO
Xlib - C Language X Interface X Version 11 libX11 1.6.0 XInitThreads(3)
All times are GMT -4. The time now is 12:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy