Linux-kernel mailing list archive 2000-23,: Re: Linux 2.5 / 2.6 TODO (preliminary)

# Re: Linux 2.5 / 2.6 TODO (preliminary)

Alan Cox (alan@lxorguk.ukuu.org.uk)
Sun, 4 Jun 2000 17:46:52 +0100 (BST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Alan Cox: "Re: [PATCH] fix for sysinfo(2) in 2.4.0-test1"
- Previous message: kuznet@ms2.inr.ac.ru: "Re: IGMP"
- Next in thread: Christopher Smith: "Re: Linux 2.5 / 2.6 TODO (preliminary)"
- Reply: Christopher Smith: "Re: Linux 2.5 / 2.6 TODO (preliminary)"

> > In glibc
>
> So is there no advantage of having something like that in the kernel, to
> allow a program to queue up many buffers for the network code to handle
> as it can, rather than either blocking on a send() or repeatedly making
> kernel calls on a nonblocking socket until it manages to send all its
> data?

You can do that with a thread from user space. In fact a lot of systems do
most of their AIO via threads in user space.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: Alan Cox: "Re: [PATCH] fix for sysinfo(2) in 2.4.0-test1"
- Previous message: kuznet@ms2.inr.ac.ru: "Re: IGMP"
- Next in thread: Christopher Smith: "Re: Linux 2.5 / 2.6 TODO (preliminary)"
- Reply: Christopher Smith: "Re: Linux 2.5 / 2.6 TODO (preliminary)"