| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
timeouts
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Once the send buffer size is increased,
there appears to be no performance advantage.
I would rather not have extra implementations.
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
| |
this fixes a bug when there are multiple mboard per device,
the occupancy int could be uninitialized to a bad value,
while subdev specs are being setup for the first time,
and cause allocation issues
|
| |
|
|
|
|
| |
basics/unknown
|
| |
|
|
|
|
| |
commit more)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
return zero
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
On OSX w/ boost 1.47, this general area of code was inconsistently barfing w/ lock error.
Perhaps its a boost bug, in any case, using it this way seems to solve the problem.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|