From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Josef Griebichler <griebichler.josef@gmx.at>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Rik van Riel <riel@redhat.com>, Paolo Abeni <pabeni@redhat.com>,
Hannes Frederic Sowa <hannes@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>, Jonathan Corbet <corbet@lwn.net>,
LMML <linux-media@vger.kernel.org>,
David Miller <davem@davemloft.net>,
torvalds@linux-foundation.org
Subject: Aw: Re: dvb usb issues since kernel 4.9
Date: Mon, 8 Jan 2018 23:16:56 +0100 [thread overview]
Message-ID: <20180108231656.3bbd1968@redhat.com> (raw)
On Mon, 8 Jan 2018 22:44:27 +0100
Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, Jan 08, 2018 at 10:31:09PM +0100, Jesper Dangaard Brouer wrote:
> > 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?...)
>
> Isn't networking also over USB on the Pi ?
Darn, that is true. Looking at the dmesg output in http://ix.io/DOg:
[ 0.405942] usbcore: registered new interface driver smsc95xx
[ 5.821104] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
I don't know enough about USB... is it possible to control which CPU
handles the individual USB ports, or on some other level (than ports)?
WARNING: multiple messages have this Message-ID (diff)
From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Josef Griebichler <griebichler.josef@gmx.at>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Rik van Riel <riel@redhat.com>, Paolo Abeni <pabeni@redhat.com>,
Hannes Frederic Sowa <hannes@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>, Jonathan Corbet <corbet@lwn.net>,
LMML <linux-media@vger.kernel.org>,
David Miller <davem@davemloft.net>,
torvalds@linux-foundation.org
Subject: Re: dvb usb issues since kernel 4.9
Date: Mon, 8 Jan 2018 23:16:56 +0100 [thread overview]
Message-ID: <20180108231656.3bbd1968@redhat.com> (raw)
In-Reply-To: <20180108214427.GT29822@worktop.programming.kicks-ass.net>
On Mon, 8 Jan 2018 22:44:27 +0100
Peter Zijlstra <peterz@infradead.org> wrote:
> On Mon, Jan 08, 2018 at 10:31:09PM +0100, Jesper Dangaard Brouer wrote:
> > 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?...)
>
> Isn't networking also over USB on the Pi ?
Darn, that is true. Looking at the dmesg output in http://ix.io/DOg:
[ 0.405942] usbcore: registered new interface driver smsc95xx
[ 5.821104] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
I don't know enough about USB... is it possible to control which CPU
handles the individual USB ports, or on some other level (than ports)?
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next reply other threads:[~2018-01-08 22:16 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 22:16 Jesper Dangaard Brouer [this message]
2018-01-08 22:16 ` dvb usb issues since kernel 4.9 Jesper Dangaard Brouer
-- strict thread matches above, loose matches on Subject: below --
2018-07-17 22:21 Mauro Carvalho Chehab
2018-07-17 22:21 ` Mauro Carvalho Chehab
2018-07-17 22:21 ` Mauro Carvalho Chehab
2018-07-17 18:07 hannah
2018-07-17 18:07 ` Hanna Hawa
2018-07-17 18:07 ` Hanna Hawa
2018-07-17 17:09 Linus Torvalds
2018-07-17 17:09 ` Linus Torvalds
2018-07-17 17:09 ` Linus Torvalds
2018-07-17 11:54 hannah
2018-07-17 11:54 ` Hanna Hawa
2018-01-13 10:46 Aw: " Mauro Carvalho Chehab
2018-01-13 10:46 ` Mauro Carvalho Chehab
2018-01-13 9:09 Aw: " Mauro Carvalho Chehab
2018-01-13 9:09 ` Mauro Carvalho Chehab
2018-01-12 21:48 Aw: " Eric Dumazet
2018-01-12 21:48 ` Eric Dumazet
2018-01-12 21:13 Aw: " Mauro Carvalho Chehab
2018-01-12 21:13 ` Mauro Carvalho Chehab
2018-01-10 9:45 Aw: " Jesper Dangaard Brouer
2018-01-10 9:45 ` Jesper Dangaard Brouer
2018-01-10 3:02 Mike Galbraith
2018-01-10 3:02 ` Mike Galbraith
2018-01-09 21:48 Aw: " Eric Dumazet
2018-01-09 21:48 ` Eric Dumazet
2018-01-09 21:26 Jesper Dangaard Brouer
2018-01-09 21:26 ` Jesper Dangaard Brouer
2018-01-09 18:58 Aw: " Linus Torvalds
2018-01-09 18:58 ` Linus Torvalds
2018-01-09 17:57 Aw: " Eric Dumazet
2018-01-09 17:57 ` Eric Dumazet
2018-01-09 17:55 Linus Torvalds
2018-01-09 17:55 ` Linus Torvalds
2018-01-09 17:48 Aw: " Linus Torvalds
2018-01-09 17:48 ` Linus Torvalds
2018-01-09 17:42 Mauro Carvalho Chehab
2018-01-09 17:42 ` Mauro Carvalho Chehab
2018-01-09 17:27 Aw: " Eric Dumazet
2018-01-09 17:27 ` Eric Dumazet
2018-01-09 16:51 Aw: " Josef Griebichler
2018-01-09 16:51 ` Josef Griebichler
2018-01-08 21:44 Peter Zijlstra
2018-01-08 21:44 ` Peter Zijlstra
2018-01-08 21:31 Aw: " Jesper Dangaard Brouer
2018-01-08 21:31 ` Jesper Dangaard Brouer
2018-01-08 20:40 Aw: " Jesper Dangaard Brouer
2018-01-08 20:40 ` Jesper Dangaard Brouer
2018-01-08 19:51 Linus Torvalds
2018-01-08 19:51 ` Linus Torvalds
2018-01-08 17:35 Aw: " Alan Stern
2018-01-08 17:35 ` Aw: " Alan Stern
2018-01-08 17:15 Aw: " Josef Griebichler
2018-01-08 17:15 ` Aw: " Josef Griebichler
2018-01-08 16:31 Aw: " Alan Stern
2018-01-08 16:31 ` Alan Stern
2018-01-08 16:26 Josef Griebichler
2018-01-08 16:26 ` Josef Griebichler
2018-01-08 16:10 Alan Stern
2018-01-08 16:10 ` Alan Stern
2018-01-08 9:43 Mauro Carvalho Chehab
2018-01-08 9:43 ` Mauro Carvalho Chehab
[not found] <trinity-35b3a044-b548-4a31-9646-ed9bc83e6846-1513505978471@3c-app-gmx-bs03>
[not found] ` <20171217120634.pmmuhdqyqmbkxrvl@gofer.mess.org>
2017-12-17 13:27 ` Mauro Carvalho Chehab
[not found] ` <trinity-1fa14556-8596-44b1-95cb-b8919d94d2d4-1515251056328@3c-app-gmx-bs15>
2018-01-06 19:54 ` Mauro Carvalho Chehab
2018-01-06 21:07 ` Aw: " Josef Griebichler
2018-01-06 21:44 ` Alan Stern
2018-01-07 11:03 ` Mauro Carvalho Chehab
2018-01-07 15:41 ` Alan Stern
2018-01-07 17:01 ` Aw: " Josef Griebichler
2018-01-07 17:01 ` Josef Griebichler
2018-01-07 21:23 ` Linus Torvalds
2018-01-08 10:02 ` Mauro Carvalho Chehab
2018-01-08 11:59 ` Jesper Dangaard Brouer
2018-01-08 12:53 ` Mauro Carvalho Chehab
2018-01-08 16:25 ` Alan Stern
2018-01-08 17:55 ` Ingo Molnar
2018-01-08 18:32 ` Linus Torvalds
2018-01-08 19:15 ` Alan Stern
2018-01-26 14:17 ` Mauro Carvalho Chehab
2018-01-26 19:37 ` Mauro Carvalho Chehab
2018-01-29 13:51 ` Mauro Carvalho Chehab
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=20180108231656.3bbd1968@redhat.com \
--to=jbrouer@redhat.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=griebichler.josef@gmx.at \
--cc=hannes@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.