public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Toth <stoth@linuxtv.org>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: linux-media@vger.kernel.org, e9hack <e9hack@googlemail.com>,
	linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [BUG] changeset 9029 (http://linuxtv.org/hg/v4l-dvb/rev/aa3e5cc1d833)
Date: Tue, 17 Feb 2009 10:16:55 -0500	[thread overview]
Message-ID: <499AD4E7.1030306@linuxtv.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0902161611300.24268@shell2.speakeasy.net>

Trent Piepho wrote:
> On Mon, 16 Feb 2009, Steven Toth wrote:
>>> Hartmut, Oliver and Trent: Thanks for helping with this issue. I've just
>>> reverted the changeset. We still need a fix at dm1105, au0828-dvb and maybe
>>> other drivers that call the filtering routines inside IRQ's.
>> Fix the demux, add a worker thread and allow drivers to call it directly.
>>
>> I'm not a big fan of videobuf_dvb or having each driver do it's own thing as an
>> alternative.
>>
>> Fixing the demux... Would this require and extra buffer copy? probably, but it's
>> a trade-off between  the amount of spent during code management on a driver by
>> driver basis vs wrestling with videobuf_dvb and all of problems highlighted on
>> the ML over the last 2 years.
> 
> Have the driver copy the data into the demuxer from the interrupt handler
> with irqs disabled?  That's still too much.
> 
> The right way to do it is to have a queue of DMA buffers.  In the interrupt
> handler the driver takes the completed DMA buffer off the "to DMA" queue
> and puts it in the "to process" queue.  The driver should not copy and
> cetainly not demux the data from the interrupt handler.

I know what the right way is Trent (see cx23885) although thank you for 
reminding me. videobuf_dvb hasn't convinced people like me to bury myself in its 
mess or complexity during retro fits cases. Retro fitting videobuf_dvb into cx18 
(at the time) was way too much effort.

Retro fitting it into existing drivers can be painful and I haven't seen any 
volunteers stand up over the last 24 months to get this done.

My suggestion? For the most part we're talking about very low data rates for 
DVB, coupled with fast memory buses for memcpy's. If the group doesn't want 
calls to the sw_filter methods then implement a half-way-house replacement for 
those drivers - as I mentioned above - with the memcpy. Either this approach, or 
make videobuf_dvb mandatory and deprecate sw_filter_...n() to intensionally 
break drivers and force maintainers to comply. This will upset people.

Realistically, this thread will probably go on for a couple of days then trail 
off into nothing. The subject will rear it's head again in a few months, like 
it's done in the past.

A general question to the group: Who wants to volunteer to retro fit 
videobuf_dvb into the current drivers so we can avoid calls to sw_filter_...n() 
directly?

I'm willing to loan any hardware I have to the volunteer assuming we can work 
out something on shipping.

- Steve


  reply	other threads:[~2009-02-17 15:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02  1:46 [BUG] changeset 9029 (http://linuxtv.org/hg/v4l-dvb/rev/aa3e5cc1d833) e9hack
2009-02-02  3:38 ` Andy Walls
2009-02-15 12:36 ` Oliver Endriss
2009-02-15 14:07   ` [linux-dvb] " Andy Walls
2009-02-15 20:25   ` Andy Walls
2009-02-16 16:19   ` Trent Piepho
2009-02-16 16:33     ` [linux-dvb] " VDR User
2009-02-16 18:31     ` Mauro Carvalho Chehab
2009-02-16 19:13       ` [linux-dvb] " Steven Toth
2009-02-16 19:15         ` Steven Toth
2009-02-16 23:11           ` Andy Walls
2009-02-17  0:22         ` Trent Piepho
2009-02-17 15:16           ` Steven Toth [this message]
2009-02-17 16:47             ` Andreas Oberritter
2009-02-18  2:32             ` Trent Piepho
2009-02-18 15:07               ` Steven Toth
2009-02-18 20:45                 ` Trent Piepho
2009-02-17  0:40     ` Oliver Endriss
2009-02-17  4:02       ` Andreas Oberritter
2009-02-18  2:04         ` [linux-dvb] " Oliver Endriss
2009-02-18  3:22           ` Trent Piepho
2009-02-18 16:47             ` Oliver Endriss
2009-02-18 12:51           ` Andreas Oberritter
2009-02-18  9:15         ` Trent Piepho

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=499AD4E7.1030306@linuxtv.org \
    --to=stoth@linuxtv.org \
    --cc=e9hack@googlemail.com \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-media@vger.kernel.org \
    --cc=xyzzy@speakeasy.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