From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Pipes and fd question. Large amounts of data.
Date: Sun, 30 Jan 2005 19:41:38 +0000 (UTC) [thread overview]
Message-ID: <ctjd9i$mvf$2@news.cistron.nl> (raw)
In-Reply-To: 200501301115.59532.ods15@ods15.dyndns.org
In article <200501301115.59532.ods15@ods15.dyndns.org>,
Oded Shimon <ods15@ods15.dyndns.org> wrote:
>I have implemented this, but it has a major disadvantage - every 'write()'
>only write 4k at a time, never more, because of how non-blocking pipes are
>done. at 20,000 context switches a second, this method reaches barely 10mb a
>second, if not less.
If you're using pipe(), you might want to try socketpair()
instead. You can setsockopt() SO_RCVBUF and SO_SNDBUF to
large values if you want.
Mike.
prev parent reply other threads:[~2005-01-30 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 9:15 Pipes and fd question. Large amounts of data Oded Shimon
[not found] ` <200501300941.45554.miles@milessabin.com>
2005-01-30 10:48 ` Oded Shimon
2005-01-31 15:02 ` Chris Friesen
2005-01-31 15:14 ` Oded Shimon
2005-01-30 19:41 ` Miquel van Smoorenburg [this message]
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='ctjd9i$mvf$2@news.cistron.nl' \
--to=miquels@cistron.nl \
--cc=linux-kernel@vger.kernel.org \
/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