public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hamad Kadmany" <hkadmany@codeaurora.org>
To: <linux-media@vger.kernel.org>
Subject: RE: [media][dvb-core] Question on dvr device copy
Date: Tue, 14 Feb 2012 09:33:50 +0200	[thread overview]
Message-ID: <000001cceaeb$00985860$01c90920$@codeaurora.org> (raw)
In-Reply-To: <000001cce991$53bf56c0$fb3e0440$@codeaurora.org>

Hi,

I would appreciate if anyone can feedback on this, I'm considering
implementing mmap in demux/dvr devices so that user-space can access the
input/output buffers directly without the need for read/write operations.

Thanks
Hamad

-----Original Message-----
From: linux-media-owner@vger.kernel.org
[mailto:linux-media-owner@vger.kernel.org] On Behalf Of Hamad Kadmany
Sent: Sunday, February 12, 2012 4:19 PM
To: linux-media@vger.kernel.org
Subject: [media][dvb-core] Question on dvr device copy 

Hi,

Currently when playing stream from memory through dvr device (through write
calls), the written buffer is copied from user-space to kernel space. The
same applies when recording a stream, the TS packets received from HW are
copied to dvr ring-buffer.

I'm a bit concerned about the performance due to the copy, and whether we
better have a memory mapped ring-buffer in dvr device output and/or dvr
device input with user-space to cope with high bitrate streams.

Your feedback on this will be mostly appreciated.

Thanks
Hamad

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2012-02-14  7:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-12 14:19 [media][dvb-core] Question on dvr device copy Hamad Kadmany
2012-02-14  7:33 ` Hamad Kadmany [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='000001cceaeb$00985860$01c90920$@codeaurora.org' \
    --to=hkadmany@codeaurora.org \
    --cc=linux-media@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