From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Oded Shimon <ods15@ods15.dyndns.org>
Cc: Miles Sabin <miles@milessabin.com>, linux-kernel@vger.kernel.org
Subject: Re: Pipes and fd question. Large amounts of data.
Date: Mon, 31 Jan 2005 09:02:14 -0600 [thread overview]
Message-ID: <41FE4876.8020507@nortelnetworks.com> (raw)
In-Reply-To: <200501301248.45538.ods15@ods15.dyndns.org>
Oded Shimon wrote:
> On Sunday 30 January 2005 11:41, Miles wrote:
>>I'd say that this was one of the rare cases where a solution using
>>threads is not only superior to one using event-driven IO, but actually
>>required.
> Yeah, I reached just about the same conclusion. At first I thought only 2
> threads were necessary, one for each data flow, but I realized a deadlock
> could happen just as well in that too. Making a 4 thread implementation I
> trust is gonna be hard... I better get working. :)
Your other option would be to use processes with shared memory (either
sysV or memory-mapped files). This gets you the speed of shared memory
maps, but also lets you get the reliability of not sharing your entire
memory space.
If you use NPTL, your locking should be quick as well. If not, you can
always roll your own futex-based locking.
Chris
next prev parent reply other threads:[~2005-01-31 15:03 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 [this message]
2005-01-31 15:14 ` Oded Shimon
2005-01-30 19:41 ` Miquel van Smoorenburg
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=41FE4876.8020507@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@milessabin.com \
--cc=ods15@ods15.dyndns.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