Messages in this thread | | | Date | Wed, 14 Mar 2001 14:55:13 -0500 (EST) | From | Alexander Viro <> | Subject | Re: system call for process information? |
| |
On Wed, 14 Mar 2001, Szabolcs Szakacsits wrote:
> > On Mon, 12 Mar 2001, Alexander Viro wrote: > > On Mon, 12 Mar 2001, Guennadi Liakhovetski wrote: > > > I need to collect some info on processes. One way is to read /proc > > > tree. But isn't there a system call (ioctl) for this? And what are those > > Occam's Razor. Why invent new syscall when read() works? > > 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...
Whether code blocks or not depends on the code, not on the calling conventions. And definitely not on ASCII vs. binary - conversion between these formats _is_ doable without blocking operations.
- 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/
| |