linux-kernel - Re: [ANNOUNCE] 4.1.5-rt5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <56BDA0EF.7090503@linutronix.de>
Date:	Fri, 12 Feb 2016 10:07:59 +0100
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Tim Sander <tim@...eglstein.org>
Cc:	linux-rt-users <linux-rt-users@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>, rostedt@...dmis.org,
	John Kacur <jkacur@...hat.com>
Subject: Re: [ANNOUNCE] 4.1.5-rt5

On 02/12/2016 09:28 AM, Tim Sander wrote:
> Hi Sebastian

Hi Tim,

> Am Sonntag, 16. August 2015, 15:56:30 schrieb Sebastian Andrzej Siewior:
>> I'm pleased to announce the v4.1.5-rt5 patch set.
> I have just tested it with a Altera SoC ARM v7. The latencies seem to have 
> gotten a little bit worse with each release. The first core has always been 
> worse (presumably due to interrupt load) but now it dropped to 111µs (rt5) 
> from 76µs(rt3) and 54µs(rt2). 

in -rt2 we had bug in migrate disable code which means each task was
running on CPU0. This got partly fixed in -rt3. In -rt3 the scheduler
could assign a task to CPU1 but the task should stay there for ever.
This little detail was fixed in -rt5.
This is one thing that comes to mind.
Lazy-preempt should have been fixed in -rt3, too. This should not give
you higher latencies but higher throughput.

What about rt4? It is only the stable update so you should see here the
numbers from rt3. If that is true and your numbers are stable it should
be easy to run git bisect between rt4 and rt5. And looking at
  https://git.kernel.org/rt/linux-rt-devel/h/v4.4.1-rt5
the only non-cosmetic change in -rt5 that should affect you is the
migrate-disable fixup from Mike.

> Best regards
> Tim

Sebastian