Re: PROPOSAL: extend pipe() to support NULL argument.

[Denys Vlasenko]

On Friday 03 July 2009 12:28, Albert ARIBAUD wrote:
> Changli Gao a Ãcrit :
> 
> > Yea, in many cases, max fd number must be enlarged. More fds means
> > more memory. Although memory is cheaper today, we have to do our best
> > to save money.
> 
> Sorry for interrupting, but I don't see how pipe could return a single fd, 
> considering there are two (partly) independent ends, each being read (resp. 
> written) in their own time, and an fd has only one "current read/write 
> position" IIUC.
> 
> If the proposal is to have two independent positions (one for reads and one 
> for writes) for a single fd, then I am not sure the gain in the number of 
> fds used is worth the loss in the increased size of the fd structure.
> 
> Am I missing something?

As I understand it, the proposal is to make pipe(NULL) return a fd,
which can be read from and written to. Whatever you write
is remembered, and can be retrieved by reads later.

standard pipe(two_fds) returns two fds. One is only used for writes.
Another is only used for reads. Which may be wasteful in some
situations (like, if you have thousands of pipes).

There is no trick I know of which may be used to "combine"
these two fds into one, close second one and thus save one fd table slot.

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