Eric Wong <[email protected]> writes: > Are you able to isolate whether $PIPE_BUFSIZ or MAX_INFLIGHT on > it's own fixes it?
MAX_INFLIGHT is sufficient. In fact, $PIPE_BUFSIZ had no effect at all when I tried just now. > And can you confirm the ->blocking(0) change had no effect on > it's own? That was the first thing I tried, and it had no effect. > Capping MAX_INFLIGHT to a smaller value is probably fine (maybe > 10 can work). I tried with 10 just now, and that was fine also. > I also do wonder if you've hit a kernel bug under low memory > conditions. I've certainly encountered problems with TCP > traffic hanging processes due to memory compaction. I doubt it. I looked during a deadlock, and I had 2.66 GiB available. -- Chris
