[vdr] Re: vdr Digest, Vol 27, Issue 5

[natalia]

[EMAIL PROTECTED] escreveu:

Send vdr mailing list submissions to
vdr@linuxtv.org

To subscribe or unsubscribe via the World Wide Web, visit
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]

You can reach the person managing the list at
[EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than Re: Contents of vdr digest...


Today's Topics:

   1. EPG messages in debug log (Risto M?ki-Pet?ys)


--

Message: 1
Date: Wed, 4 Apr 2007 14:02:30 +0300
From: Risto M?ki-Pet?ys [EMAIL PROTECTED]
Subject: [vdr] EPG messages in debug log
To: vdr@linuxtv.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1

I'm using vdr v1.4.6 on Debian Etch from e-tobi's packages and my dvb-c card
is connected to HTV, Helsinki area cable television network. I get this sort
of events in debug log, should they be noticed?

Mar 20 07:08:26 digi vdr: [6633] =
Mar 20 07:08:26 digi vdr: [6633] EPG bugfix statistics
Mar 20 07:08:26 digi vdr: [6633] =
Mar 20 07:08:26 digi vdr: [6633] IF SOMEBODY WHO IS IN CHARGE OF THE EPG DATA 
FOR ONE OF THE LISTED
Mar 20 07:08:26 digi vdr: [6633] CHANNELS READS THIS: PLEASE TAKE A LOOK AT THE 
FUNCTION cEvent::FixEpgBugs()
Mar 20 07:08:26 digi vdr: [6633] IN VDR/epg.c TO LEARN WHAT'S WRONG WITH YOUR 
DATA, AND FIX IT!
Mar 20 07:08:26 digi vdr: [6633] =
Mar 20 07:08:26 digi vdr: [6633] Fix^IHits^IChannels
Mar 20 07:08:26 digi vdr: [6633] 2^I1274^ICanal+ Film 1, DSC TravelLiving, DSC 
Civilization, Canal+ Sport 2, CNBC Nordic, ...
Mar 20 07:08:26 digi vdr: [6633] 3^I557^IBloomberg English TV, Viasat Explorer, 
TV1000 Family, TV1000 Nordic, EuroNews, ...
Mar 20 07:08:26 digi vdr: [6633] 4^I3^I3sat, FRANCE 2
Mar 20 07:08:26 digi vdr: [6633] 6^I563^ITV2, Barnkanal, SHOW TV, Star, MTV, 
Showtime, TV1, YLE24, YLE Teema, TGRT, Urheilukanava, ...
Mar 20 07:08:26 digi vdr: [6633] 7^I3^IFRANCE 2
Mar 20 07:08:26 digi vdr: [6633] 8^I4^IFRANCE 2
Mar 20 07:08:26 digi vdr: [6633] 9^I184^IBarnkanal, SVT1, TV2, TV1, FST5, 
YLE24, YLE Teema, JIM, Urheilukanava, MTV3 MAX, ...
Mar 20 07:08:26 digi vdr: [6633] 10^I4^IFRANCE 2
Mar 20 07:08:26 digi vdr: [6633] 11^I84^ITV2, TV1, FST5, YLE24, YLE Teema, YLE 
PEILI, JIM, Urheilukanava, YLEN KLASSINEN, ...
Mar 20 07:08:26 digi vdr: [6633] 12^I36^IFST5, MTV3 MAX, MTV3 Fakta, SVT2, 
Barnkanal, TV2, MTV3 Leffa
Mar 20 07:08:26 digi vdr: [6633] =

  



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] [PATCH] limit streamdev client's ringbuffer timeouts to more sane values

[Artur Skawina]

Well, the streamdev-client reads data from a ringbuffer and when there isn't 
anything
to read it tries to sleep for 1us and loops. This wasn't a problem when the 
timer
resolution was in the 1000..1us range (1000..100Hz); the usleep(1) call 
slept
for one or more milliseconds.
With the high-res timers in kernel 2.6.21+ usleep(1) is no longer treated as
usleep(1) and the streamdev client is almost unusable; it uses most of the 
cpu
and causes hundreds of thousands context switches per second.
This gets rid of the almost-busy-loop.

artur

diff -urNp streamdev.org/client/filter.c streamdev/client/filter.c
--- streamdev.org/client/filter.c   2005-11-06 17:43:58.0 +0100
+++ streamdev/client/filter.c   2007-04-05 23:25:11.0 +0200
@@ -57,6 +57,7 @@ cStreamdevFilters::cStreamdevFilters(voi
cThread(streamdev-client: sections assembler) {
m_Active = false;
m_RingBuffer = new cRingBufferLinear(MEGABYTE(1), TS_SIZE * 2, true);
+   m_RingBuffer-SetTimeouts(10, 10);
Start();
 }

@@ -111,8 +112,7 @@ void cStreamdevFilters::Action(void) {
}
}
m_RingBuffer-Del(TS_SIZE);
-   } else
-   usleep(1);
+   }
}
 }



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [PATCH] limit streamdev client's ringbuffer timeouts to more sane values

[Stone]

On 4/5/07, Artur Skawina [EMAIL PROTECTED] wrote:


Well, the streamdev-client reads data from a ringbuffer and when there
isn't anything
to read it tries to sleep for 1us and loops. This wasn't a problem when
the timer
resolution was in the 1000..1us range (1000..100Hz); the usleep(1)
call slept
for one or more milliseconds.
With the high-res timers in kernel 2.6.21+ usleep(1) is no longer treated
as
usleep(1) and the streamdev client is almost unusable; it uses most of
the cpu
and causes hundreds of thousands context switches per second.
This gets rid of the almost-busy-loop.




How about his approach?

--- streamdev/client/filter.c.orig  2007-04-05 20:45:04.0 -0700
+++ streamdev/client/filter.c   2007-04-05 20:45:44.0 -0700
@@ -135,7 +135,7 @@
   }
   m_RingBuffer-Del(TS_SIZE);
   } else
-   usleep(1);
+   cCondWait::SleepMs(1);
   }
}
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr