From: Oded Shimon <ods15@ods15.dyndns.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
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 17:14:08 +0200 [thread overview]
Message-ID: <200501311714.08672.ods15@ods15.dyndns.org> (raw)
In-Reply-To: <41FE4876.8020507@nortelnetworks.com>
On Monday 31 January 2005 17:02, Chris Friesen wrote:
> 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.
To be honest, most of that was gibrish to me (NTPL, futex, sysV..).. Most of
my experience with system calls is with pipes and files, I know very little
about these other things...
Either way, you are a bit late, just half an hour ago, I have completed my
program, and it works. :) I finished the pthread instead of select()
implementation pretty quickly (now I understand why lazy programmers use
threads.. heh), what took me so long was troubles with the 2 other programs,
had to refine their command line params carefully...
(btw, the 2 other programs - MPlayer and MEncoder, and my job was transferring
video AND audio between them.)
Thankyou for the reply,
- ods15
next prev parent reply other threads:[~2005-01-31 15:14 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
2005-01-31 15:02 ` Chris Friesen
2005-01-31 15:14 ` Oded Shimon [this message]
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=200501311714.08672.ods15@ods15.dyndns.org \
--to=ods15@ods15.dyndns.org \
--cc=cfriesen@nortelnetworks.com \
--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®