linux-kernel - Re: [PREEMPT RT] SLUB and split softirq lock for v3.2-rt

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: <5122DB72.7030100@huawei.com>
Date:	Tue, 19 Feb 2013 09:54:58 +0800
From:	Li Zefan <lizefan@...wei.com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	<linux-kernel@...r.kernel.org>, <linux-rt-users@...r.kernel.org>,
	Carsten Emde <C.Emde@...dl.org>
Subject: Re: [PREEMPT RT] SLUB and split softirq lock for v3.2-rt

On 2013/2/14 1:24, Steven Rostedt wrote:
> On Wed, 2013-02-13 at 17:11 +0100, Sebastian Andrzej Siewior wrote:
>> 3.2-rt is a long term supported kernel, which lacks two RT features
>> from 3.6: SLUB support and the split softirq lock implementation.
>>
>> SLUB has a way better performance than SLAB on RT and the split
>> softirq lock implementation is necessary especially for realtime
>> networking applications.
>>
>> The following patch series backports these features to 3.2-rt.
>>
>> Steven, could you please apply these patches to a separate
>> 3.2-rt-features branch?
> 
> Is it possible to separate these two features into two different patch
> sets. I would like to apply the softirq changes first, and then apply
> the slub changes.
> 
> Although it looks as though the first half is softirq only 1-8, and the
> second half is slub related 9-16. If that's the case, I'll just pull in
> 1-8 first, play with them, and then do 9-16.
> 

We've also ported these two features to 3.4-rt. Do you want us to post
them?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/