From: Oded Shimon <ods15@ods15.dyndns.org>
To: Miles Sabin <miles@milessabin.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Pipes and fd question. Large amounts of data.
Date: Sun, 30 Jan 2005 12:48:45 +0200 [thread overview]
Message-ID: <200501301248.45538.ods15@ods15.dyndns.org> (raw)
In-Reply-To: <200501300941.45554.miles@milessabin.com>
On Sunday 30 January 2005 11:41, Miles wrote:
> My suggestion would be to perform blocking writes in a seperate thread
> for each of the two written-to fds. You can still use select/poll for
> the read side ... tho' once you're using threading on the write side it
> might be more straightforward to to use threading on the read side as
> well. Bear in mind that if you do that you'll need to dedicate threads
> to _each_ of the four fds, because each of them could block
> independently while progress is required on one or more of the others.
>
> 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. :)
Thanks for the reply,
- ods15
next prev parent reply other threads:[~2005-01-30 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 9:15 Oded Shimon
[not found] ` <200501300941.45554.miles@milessabin.com>
2005-01-30 10:48 ` Oded Shimon [this message]
2005-01-31 15:02 ` Chris Friesen
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=200501301248.45538.ods15@ods15.dyndns.org \
--to=ods15@ods15.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@milessabin.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
all inboxes | Powered by JetHome®