Re: read() called twice for /proc files

• Next message: Rik van Riel: "Re: weird memory related problems, negative memory usage or fake memory usage?"
• Previous message: Rik van Riel: "Re: 2.4.10 much better than previous 2.4.x :-)"
• In reply to: Tim Hockin: "read() called twice for /proc files"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

   From: Tim Hockin <thockin@sun.com>
   Date: Mon, 24 Sep 2001 18:29:49 -0700
   
   This results in the actual read taking twice as long. Perhaps I am missing
   something...

EOF isn't known until you return the zero. You can watch the loff_t
arg to the read operation to see if it is at the end, and if so just
avoid retouching the device or whatever and go straight to returning
0.

Franks a lot,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Rik van Riel: "Re: weird memory related problems, negative memory usage or fake memory usage?"
• Previous message: Rik van Riel: "Re: 2.4.10 much better than previous 2.4.x :-)"
• In reply to: Tim Hockin: "read() called twice for /proc files"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Sep 30 2001 - 21:00:28 EST