Date: Fri, 31 Jul 2015 13:55:03 +0200 From: Svatopluk Kraus <onwahe@gmail.com> To: Hans Petter Selasky <hps@selasky.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: DWC OTG TX path optimisation for 11-current Message-ID: <CAFHCsPXFJ_XhVsT1bRw=d20Mz=cbYdmwNNLvfs_cxJvEo8B6LA@mail.gmail.com> In-Reply-To: <55BB3CC6.4030002@selasky.org> References: <55A7D8CE.4020809@selasky.org> <CAHNYxxMp9jGDbV-5=-cE6daR-O3eN5pdvO1s-=QfX=A9XYqYmA@mail.gmail.com> <55B23276.8090703@selasky.org> <CAHNYxxNc9uB62hHEv1PM9PcsGgUs=zsvNgatqLD0p%2BiiDA3Aiw@mail.gmail.com> <55B73113.2020308@selasky.org> <CAFHCsPVaPZpqXLS7OApa=Xz5VLnLjVpV5dYV8Pn2uHh1Lcz7Tg@mail.gmail.com> <55B8AB76.7030603@selasky.org> <CAFHCsPUMaYEwJsaGUFuw9yZi_5bmraSBsOYpRWvSeuebpXBJUA@mail.gmail.com> <55B8B297.1010008@selasky.org> <CAFHCsPVGLs8j6LAV%2Bg4rP_ueTOd8pUOupYFGvmgC3XGcJC720Q@mail.gmail.com> <20150729154516.GH78154@funkthat.com> <55B8F5EC.2050908@selasky.org> <46ad096c958.1a82a175@mail.schwarzes.net> <55B9C3E2.5040501@selasky.org> <46ae815c7c3.447237c8@mail.schwarzes.net> <46aece00b53.3c1cdc1f@mail.schwarzes.net> <55BB2A5F.9000502@selasky.org> <55BB3CC6.4030002@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 31, 2015 at 11:15 AM, Hans Petter Selasky <hps@selasky.org> wrote: > Hi, > > I did some testing myself and I see the polling handler can loop many times > when USB is active. Instead of 2 as a polling limit I've set 16. Hope this > works too. Works fine over here. > > https://svnweb.freebsd.org/changeset/base/286118 > Definitely, some limitation was needed there. Thanks. Unfortunatelly, it turned out that it does not help with my problem. It has affected system response time in good way for some time after the trigger is pulled. However, after 17 hours when buildworld finished, system response time is bad again. It also turns out that I have a problem with booting my kernels. So I cannot test the extra "clear RX FIFO level interrupt" patch as even this one line of code causes that kernel does not boot. It freezes at very beginning and even first printf is not printed. Thus I have to debug this problem firstly. It will be very funny without either jtag or early printf. ;) Meantime, I have noticed that after reboot (system is 99% idle), I'm getting the following output from vmstat: root@rpi2:~ # vmstat -i -w 1 interrupt total rate irq1: mbox0 27 0 irq2: vchiq0 6 0 irq17: bcm283x_dwco 2266826 20654 irq26: bcm_dma0 962 9 irq65: uart0 21516 196 irq70: sdhci_bcm0 556 5 irq73: generic_time 25952 236 irq76: ipi 23182 211 Total 2339027 21312 irq1: mbox0 0 0 irq2: vchiq0 0 0 irq17: bcm283x_dwco 25734 23983 irq26: bcm_dma0 0 0 irq65: uart0 527 491 irq70: sdhci_bcm0 0 0 irq73: generic_time 245 228 irq76: ipi 99 92 Total 26605 24795 irq1: mbox0 0 0 irq2: vchiq0 0 0 irq17: bcm283x_dwco 25679 24022 irq26: bcm_dma0 0 0 irq65: uart0 476 445 irq70: sdhci_bcm0 0 0 irq73: generic_time 246 230 irq76: ipi 100 94 Total 26501 24790 irq1: mbox0 0 0 irq2: vchiq0 0 0 irq17: bcm283x_dwco 25683 24025 irq26: bcm_dma0 0 0 irq65: uart0 476 445 irq70: sdhci_bcm0 0 0 irq73: generic_time 245 229 irq76: ipi 104 97 Total 26508 24797 IMO, 24000 interrupts per a second for bcm283x_dwco is too many. Svata > --HPS > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFHCsPXFJ_XhVsT1bRw=d20Mz=cbYdmwNNLvfs_cxJvEo8B6LA>