d9b1a3f03e
need to do it directly, since ttwwakeup() is always called just before returning from rpstart(). The brokenness was waking up the wrong address after clearing TS_SO_OLOWAT. It's not clear how processes waiting for output to drain below low water ever got woken up. Found by: when I fixed longstanding warts in output watermark handling, this was the only driver that knew too much (anything) about the watermarks |
||
---|---|---|
.. | ||
rp.c | ||
rpreg.h | ||
rpvar.h |