Printable View
im trying to implement a multiclient tcp/ip chat and in the server side im spawning threads for every client. but during execution the processor is executing only one thread and the main thread. is there any way to manually switch the threads for cpu time after some time say 10secs or like that?
Once created the OS should schedule the thread automatically unless they are blocked/suspended.
Which OS are you using?
On Windows, no. You can set priority to how much cpu time they should get and how often they should be rescheduled but nothing aside from that.
im doin it in unix using gcc.
Presumably each thread is waiting on say a socket for something interesting to happen?
My preferred way would be to use select() with a timeout if you want each thread to run every so often, even if there is no network traffic.
hmmm..... me even thinkin so to use select but i almost did the entire thing based on thread now have to find a way to change the existin code.....
select() with a timeout can do a lot of what most people rush headlong into threads as being "the only solution".
is there any way really to schedule threads manually??
I doubt there would be in any operating system. It messes up thread scheduling.
ok........ no other go have to go up with select call only.....
thank you all.
Why would you want to do that? Or perhaps I should put it another way: Why would any sensible OS producer want to do that? The best place to decide which thread to run has to be in the OS - it is the only part of the system that KNOWS what is going on.Quote:
Originally Posted by gopal_85
You can make threads go to sleep on your say so, but the only way that a particular thread will be made running is if the OS decides that it should run.
What is making the "only one thread" situation? Are you perhaps spinning around performing some waiting task by polling if something is available?
Also, in Unix/Linux/Windows, multiple threads should be time-sharing, so even if you start 10 threads, they will be sharing the CPU, and the time-quanta that one thread can use up at any given time before another runnable thread can be run should be much less than a second - so if 10 threads can run, they should all run at least once a second, probably more often. So you may want to look into why your threads are NOT behaving this way - perhaps you are causing the other threads to block for some reason [this may include reading from a shared resource which leads to ONE thread getting most of the time].
--
Mats
You are probably using blocking sockets and one or more of your sockets are blocking causing a threadlock. Your threads should behave as matsp described it and if they are not something else is wrong.
Yeah what matsp told is right there was a block and as i removed that block it is now working properly...