From: "David Härdeman" <david@hardeman.nu>
To: linux-kernel@vger.kernel.org
Subject: splice question
Date: Sun, 12 Aug 2007 18:28:20 +0200 [thread overview]
Message-ID: <20070812162820.GA26892@hardeman.nu> (raw)
I'm currently toying with splice. The test program I have sends a MPEG2
transport stream from a dvb card and sends it to N clients via http.
Since the dvb frontend driver doesn't support splice
(linux/drivers/media/dvb/dvb-core/dmxdev.c I guess, anyone interested in
adding splice support to it?) I had to do a normal read() to a
user-space buffer and then write that to a pipe.
Once the data is in the pipe, my idea was to tee() from the pipe to each
client socket using nonblocking ops, and then consume the data by
splicing it to /dev/null.
The problem is that tee() doesn't support sockets. Is this a limitation
that would be easy to fix?
Otherwise I guess I'd have to add a second pipe, then (in a loop)
tee() from the first to the second pipe and then splice from the
second pipe to a socket. Doesn't sound very elegant and would need quite
a lot of extra syscalls.
--
David Härdeman
next reply other threads:[~2007-08-12 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 16:28 David Härdeman [this message]
2007-08-12 19:41 ` splice question Linus Torvalds
2007-08-12 20:56 ` David Härdeman
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=20070812162820.GA26892@hardeman.nu \
--to=david@hardeman.nu \
--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