To call a function repeatedly after certain period

Quote:

---

It may well "work" as long as your system is lightly loaded and allows your two threads to run most of the time, but it's certianly not a robust design

---

Thanks for the advice.Is there any other idea for the problem.Actually for every 1000 millisecond i get the data from external source .

Quote:

---

Originally Posted by babu198649

Thanks for the advice.Is there any other idea for the problem.Actually for every 1000 millisecond i get the data from external source .

---

So I take it that the application waits on some sort of indication that data is available, right? And when you receive that indication, you copy the data to an array or some such.

If that's the case, your second thread should be waiting for a semaphore, then when your copying is finished, you signal that semaphore and that lets the second thread run.

This is pretty normal way of solving this sort of problem.

--
Mats

Quote:

---

It may well "work" as long as your system is lightly loaded and allows your two threads to run most of the time, but it's certianly not a robust design.

---

Thanks for u r advice . Actually i want to collect data from external source every 1000 milliseconds and store it in circular buffer.In the other thread the data is computed which is time consuming.Any suggestions would be a great help for me.

Quote:

---

Originally Posted by babu198649

Thanks for u r advice . Actually i want to collect data from external source every 1000 milliseconds and store it in circular buffer.In the other thread the data is computed which is time consuming.Any suggestions would be a great help for me.

---

Then you should use a os implemented queue or pipe to forward the data to the processing thread. You probably shouldn't try to implement your own queue using a circular buffer, as that tends to cause subtle bugs that only happen when you have the system in production. The processing thread should read from the queue/pipe.

If for some reason the queue/pipe implementation is relatively limited and you write lots of data, you could allocate memory buffers for a few blocks of data, and use a two-way communication where you free a buffer when it's processing is completed (perhaps using a third thread for this work), and only pass the address of the new data to the processing thread - that would prevent the overhead of writing lots of data an possibly blocking on the writing operation

--
Mats

Thanks for the idea.I understood the idea.But the problem is i dont know how to send data through queue and receive from queue.Are there any libraries to do that.

Quote:

---

Originally Posted by babu198649

Thanks for the idea.I understood the idea.But the problem is i dont know how to send data through queue and receive from queue.Are there any libraries to do that.

---

What OS are you using?

--
Mats

linux(RHEL4)


[babu@localhost aaff]$ uname -a
Linux localhost.localdomain 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:32:14 EDT 2005 i686 i686 i386 GNU/Linux

One of the first hits on google for "interthread communication" is this:
http://freshmeat.net/projects/itc/

Not sure if it's any good or not, but I'd expect it's better than rolling your own.

--
Mats

Thanks for the keyword "interthread communication" i will search more ,implement and then will post the problems.