All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@free.fr>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Changli Gao <xiaosuo@gmail.com>,
	Amerigo Wang <xiyou.wangcong@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: PROPOSAL: extend pipe() to support NULL argument.
Date: Fri, 03 Jul 2009 12:28:36 +0200	[thread overview]
Message-ID: <4A4DDD54.9030206@free.fr> (raw)
In-Reply-To: <412e6f7f0907030259m5556ee2fobbb58d377bce4d17@mail.gmail.com>

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?

Amicalement,
-- 
Albert.

  parent reply	other threads:[~2009-07-03 10:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02  7:36 PROPOSAL: extend pipe() to support NULL argument Changli Gao
2009-07-02  9:13 ` Amerigo Wang
2009-07-02  9:18   ` Changli Gao
2009-07-02  9:46     ` Amerigo Wang
2009-07-02 10:04       ` Changli Gao
2009-07-02 10:21         ` Amerigo Wang
2009-07-03  0:43           ` Changli Gao
2009-07-03  1:55             ` Amerigo Wang
2009-07-03  2:10               ` Changli Gao
2009-07-03  3:00                 ` Amerigo Wang
2009-07-03  4:08                   ` Changli Gao
2009-07-03  5:19                     ` Amerigo Wang
2009-07-03  5:42                       ` Changli Gao
2009-07-03  7:15                         ` Amerigo Wang
2009-07-03  7:40                           ` Changli Gao
2009-07-03  8:16                             ` Amerigo Wang
2009-07-03  8:27                               ` Changli Gao
2009-07-03  9:42                                 ` Amerigo Wang
2009-07-03  9:59                                   ` Changli Gao
2009-07-03 10:23                                     ` Amerigo Wang
2009-07-03 10:28                                     ` Albert ARIBAUD [this message]
2009-07-06  1:12                                       ` Changli Gao
2009-07-06  6:15                                         ` Albert ARIBAUD
2009-07-06  6:23                                           ` Changli Gao
2009-07-06  6:30                                             ` Albert ARIBAUD
2009-07-07  4:43                                       ` Denys Vlasenko
2009-07-07  7:45                                         ` Changli Gao
2009-07-07 20:37                                           ` David Newall
2009-07-07 21:02                                             ` Zan Lynx
2009-07-08  4:41                                               ` Changli Gao
2009-07-08  4:43                                                 ` David Newall
2009-07-02 10:42     ` Alan Cox
2009-07-03  0:45       ` Changli Gao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A4DDD54.9030206@free.fr \
    --to=albert.aribaud@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xiaosuo@gmail.com \
    --cc=xiyou.wangcong@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.