From: Zan Lynx <zlynx@acm.org>
To: David Newall <davidn@davidnewall.com>
Cc: Changli Gao <xiaosuo@gmail.com>,
Denys Vlasenko <vda.linux@googlemail.com>,
Albert ARIBAUD <albert.aribaud@free.fr>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Amerigo Wang <xiyou.wangcong@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: PROPOSAL: extend pipe() to support NULL argument.
Date: Tue, 07 Jul 2009 15:02:19 -0600 [thread overview]
Message-ID: <4A53B7DB.5050105@acm.org> (raw)
In-Reply-To: <4A53B202.9080505@davidnewall.com>
David Newall wrote:
> Changli Gao wrote:
>> mkfifo(name);
>> open(name, O_RDWR);
>> unlink(name);
>>
>> Is it a trick?
>
> This does beg the question, why is it necessary to "extend" pipe() in
> this way?
Well, to me it sounds like the goal of the proposal is for very high
load, high performance socket servers so efficiency matters.
The above is more than 3 times as expensive as one pipe(). Each syscall
is thousands of machine cycles in overhead. In addition to that all
three are VFS operations which as I recall are even more expensive than
other syscalls.
But perhaps mkfifo(NULL) should be the syscall chosen to extend since
its parameters are much like open() already, and it seems to work in the
above sequence to create a one-FD FIFO already.
Or instead of, or in addition to a NULL name argument, its mode argument
could be used as a flags argument to specify an anonymous fifo creation
with FD return.
--
Zan Lynx
zlynx@acm.org
"Knowledge is Power. Power Corrupts. Study Hard. Be Evil."
next prev parent reply other threads:[~2009-07-07 21:02 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
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 [this message]
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=4A53B7DB.5050105@acm.org \
--to=zlynx@acm.org \
--cc=albert.aribaud@free.fr \
--cc=davidn@davidnewall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@googlemail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox