Messages in this thread | | | Date | Wed, 14 Mar 2001 15:21:17 -0500 (EST) | From | Alexander Viro <> | Subject | Re: system call for process information? |
| |
On Wed, 14 Mar 2001, Szabolcs Szakacsits wrote:
> > On Wed, 14 Mar 2001, Alexander Viro wrote: > > On Wed, 14 Mar 2001, Szabolcs Szakacsits wrote: > > > read() doesn't really work for this purpose, it blocks way too many > > > times to be very annoying. When finally data arrives it's useless. > > Huh? Take code of your non-blocking syscall. Make it ->read() for > > relevant file on /proc or wherever else you want it. See read() not > > blocking... > > Sorry I should have quoted "blocks". Problem isn't with blocking but > *no* data, no information. In the end you can conclude you know > *nothing* what happend in the last t time interval - this can be second, > minutes even with an RT, mlocked, etc process when the load is around 0.
And how will a new syscall avoid the same problems you have with read()? Again, they can share the payload code - it's a matter of calling conventions and layout of the output. _That_ part doesn't take long. If reading is too slow - too bad, changing the syscall number won't help.
- 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/
| |