[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180108223109.66c91554@redhat.com>
Date: Mon, 8 Jan 2018 22:31:09 +0100
From: Jesper Dangaard Brouer <jbrouer@...hat.com>
To: "Josef Griebichler" <griebichler.josef@....at>
Cc: "Mauro Carvalho Chehab" <mchehab@...pensource.com>,
"Alan Stern" <stern@...land.harvard.edu>,
"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
linux-usb@...r.kernel.org, "Eric Dumazet" <edumazet@...gle.com>,
"Rik van Riel" <riel@...hat.com>,
"Paolo Abeni" <pabeni@...hat.com>,
"Hannes Frederic Sowa" <hannes@...hat.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
"Jonathan Corbet" <corbet@....net>,
LMML <linux-media@...r.kernel.org>,
"Peter Zijlstra" <peterz@...radead.org>,
"David Miller" <davem@...emloft.net>, torvalds@...ux-foundation.org
Subject: Re: dvb usb issues since kernel 4.9
On Mon, 8 Jan 2018 17:26:10 +0100
"Josef Griebichler" <griebichler.josef@....at> wrote:
> I tried your mentioned patch but unfortunately no real improvement for me.
> dmesg http://ix.io/DOg
> tvheadend service log http://ix.io/DOi
>
> Errors during recording are still there.
Are you _also_ recording the stream on the Raspberry Pi?
It seems to me, that you are expecting too much from this small device.
> Errors increase if there is additional tcp load on raspberry.
I did expected the issue to get worse, when you load the Pi with
network traffic, as now the softirq time-budget have to be shared
between networking and USB/DVB. Thus, I guess you are running TCP and
USB/mpeg2ts on the same CPU (why when you have 4 CPUs?...)
If you expect/want to get stable performance out of such a small box,
then you (or LibreELEC) need to tune the box for this usage. And it
does not have to be that complicated. First step is to move IRQ
handling for the NIC to another CPU and than the USB port handling the
DVB signal (/proc/irq/*/smp_affinity_list). And then pin the
userspace process (taskset) to another CPU than the one handling
USB-softirq.
> Unfortunately there's no usbmon or tshark on libreelec so I can't
> provide further logs.
Do you have perf or trace-cmd on the box? Maybe we could come up with
some kernel functions to trace, to measure/show the latency spikes?
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
Powered by blists - more mailing lists