Attention is currently required from: Jolly.
Patch set 1:Code-Review -1
1 comment:
Patchset:
Are you sure this won't break any existing applications? So far we did not push this responsibility into applications. An application can just enqueue data into the write queue, and it's the responsibility of e1_input to sned it with the speed that the driver/hardware/network supports.
For DAHDI and osmo-e1d, we have file descriptors (device node, unix domain socket) which simply block once the transmit buffer is full and the line is not consuming data at the rate that is arriving from the application. So the flow/rate is controlled by the file descriptor becoming write-able.
And exactly this is where mISDN differs, and libosmo-abis/e1_input needs to ensure the same semantics towards the application.
marking as -1 until we are absolutely certain
To view, visit change 30450. To unsubscribe, or for help writing mail filters, visit settings.