gparmer/Composite — pull request #28 by rezie2 (2012-09-23 14:12:19+00:00)
Title: Sender, Receiver, and tunReceiver files

There are 3 new files in total.

The number of iterations that we go through is defined through a constant at the top of both receiver files; the client needs to be terminated manually (which would be how the original version did it). Currently the number of iterations is defined to be 10.

As far as taking averages, that is not in place. Both receiver files have an array in place which is populated with the time through the timer thread.

I'm not _entirely_ sure I have the tun receiver correct. After removing the additional code from the original, too-complex version, there really isn't that much of a difference compared to the non-tun receiver code, so I am hesitant to say whether I got it correct or not. It seems to be able to receive the messages from the client.

Lastly, the receiving message size is defined as "100" right now, in the read() function in both receiver's receive threads. That can probably be changed easily. The receive threads are passed the command line arguments during pthread_create(), so the msg_size can be pulled from there.

I didn't actually use the rlimit that you mentioned on Wednesday - I'm not sure at this point what I should be doing with that. I seem to recall that you mentioned that we should give the processes most of the CPU resources? I did set the thread priorities so that the timer has a priority of 98 and the receiver thread has a priority of 99, which was the max value I got when I sched_get_priority_max() function.

I think that's all I have to mention at this moment.

PS: This is the first time I did a pull request, so I hope I did this correctly.