I am getting a hang with lmbench 3.0, latest release, when using lat_mem_rd -N 1 96m 256
After looking at the code, I noticed that lib_timing.c makes several calls to read() & write() but never checks the return code for success or number of bytes read/written. I think this could be my problem...since the return codes are never checked, if any of these
calls fail, it is never retried....? Which hangs the parent waiting for the child(s), or hangs the child(s) waiting for the parent.
Any reason why the return codes are not checked? Obviously, read()/write() can fail or only process a portion of the bytes.
Log in to post a comment.