Date: Fri, 25 Sep 2015 00:28:39 +0200 (CEST) From: Andreas Schwarz <freebsd.asc@strcmp.org> To: Svatopluk Kraus <onwahe@gmail.com> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, Hans Petter Selasky <hps@selasky.org> Subject: Re: DWC OTG TX path optimisation for 11-current Message-ID: <46f856107c4.4a22ef6d@mail.schwarzes.net> In-Reply-To: <CAFHCsPUgOwCTeqLUa8dZygQaJ%2BdbR4cbXNg_C_cv%2B6AagvwQMg@mail.gmail.com> 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> <46baa16c4ce.6efd29ef@mail.schwarzes.net> <55CF31A1.5080205@selasky.org> <46ce372c895.20050775@mail.schwarzes.net> <46d0a4441bb.41f6f91d@mail.schwarzes.net> <55DD5C0A.2050401@selasky.org> <CAFHCsPVTpnd2RB4d0NvLRf9WniSkBPajJYABoPOuS4NKo%2BZ7PA@mail.gmail.com> <46d8b55830c.48a059ec@mail.schwarzes.net> <46e495e484.66704618@mail.schwarzes.net> <CAFHCsPUgOwCTeqLUa8dZygQaJ%2BdbR4cbXNg_C_cv%2B6AagvwQMg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24.09.15, Svatopluk Kraus wrote: > I finally found a way how to get something what could be analyzed > considering the problem with smcs warnings, slow console response, and > other oddities. And it was Michal Meloun who figured out how the > problem comes up. He was so enthusiastic and fast that he got me no > chance, no chance at all to figure it out myself. ;)) Thanks goes to > Bob Prohaska too who pointed me to stress2 which triggers the problem > even with all KTR classes compiled in kernel. This could explain why the legacy BSD scheduler was so stable compared to ULE. I'll patch and start my buildworld loop test (which will take a week (10 loops)). -asc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46f856107c4.4a22ef6d>