| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
options
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
renamed print warning calls in the implementation
fixed issue with dict::pop so it now works even if the value is not comparable
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Updated existing bandwidth property to reflect double-sided
bandwidth rather than lowpass bandwidth
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
suffix for XCVR board cnames
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
gets for BW in the wrappers
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| | |
into headers
|
| | |
|
| | |
|
| | |
|
|/
|
|
| |
unit tests
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This may fix some of our woes when the host cannot keep up.
That is, with a smaller booty, the managed buffers will get
freed up and the call to get buffer will never block waiting
for a buffer to become free. This has several side effects:
1)
Overflows are more likely to occur in the pirate thread.
Pirate-based overflows will overwrite old packets, whereas
socket-based overflows will discard newer incoming packets.
2)
The pirate thread will continue to pull in async packets
rather than loosing them in a socket-based overflow.
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|