[Sis-SCPS-INTEREST] New SCPS RI Release on Open Channel
Software...
Feighery, Patrick D.
feighery at mitre.org
Wed Mar 15 15:07:52 EST 2006
When I used the term 'poll' I used that term loosely. Before this new
release, the SCPS RI did use select(). However it returned immediately
and did not have any timeout specified. This code was originally
written over 10 years ago. Now the code has a select that will wait
for 1 msec before it times out. After doing this I realized that the
rate control token bucket was affected, so I made that change as well.
After this I realized that there were a couple of other tricks I needed
to do.
As for Eventpoll (linux) and kqueue/kevent (BSDs) I really am not
familiar with either. If you or someone else wanted to create this
functionality and have it conditionally compiled, I would be happy to
look at it.
Best regards
Pat
>>-----Original Message-----
>>From: Otto Solares [mailto:solca at guug.org]
>>Sent: Tuesday, March 14, 2006 6:50 PM
>>To: Feighery, Patrick D.
>>Cc: sis-scps-interest at mailman.ccsds.org
>>Subject: Re: [Sis-SCPS-INTEREST] New SCPS RI Release on Open
>>Channel Software...
>>
>>On Mon, Mar 13, 2006 at 01:06:22PM -0500, Feighery, Patrick D. wrote:
>>> <snip>
>>> 2) While we are on the subject of rate control and CPU
>>> resources. As I'm sure you all are aware of, the SCPS
>>process tends to
>>> be a CPU hog - to put it mildly... This was intentional,
>>because the
>>> SCPS RI constantly polls the internal sockets to read
>>packets from the
>>> kernel as soon as possible. This unfortunately means the
>>SCPS reference
>>> implementation will consume all available CPU resources that it
can.
>>
>>It is possible to change this behavior to use select() or newer
>>mechanisms like eventpoll (linux) and kqueue/kevent (BSDs) ??
>>
>>That will make a big difference in CPU utilization.
>>
>>-otto
>>
More information about the Sis-SCPS-INTEREST
mailing list