linux-kernel - Re: [patch] queued spinlocks (i386)

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] [day] [month] [year] [list]

Date:	Fri, 30 Mar 2007 00:44:44 -0400
From:	"Lee Revell" <rlrevell@...-job.com>
To:	"Nick Piggin" <npiggin@...e.de>
Cc:	"Davide Libenzi" <davidel@...ilserver.org>,
	"Oleg Nesterov" <oleg@...sign.ru>,
	"Ravikiran G Thirumalai" <kiran@...lex86.org>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Nikita Danilov" <nikita@...sterfs.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Eric Dumazet" <dada1@...mosbay.com>
Subject: Re: [patch] queued spinlocks (i386)

On 3/29/07, Nick Piggin <npiggin@...e.de> wrote:
> On Thu, Mar 29, 2007 at 10:06:41PM -0400, Lee Revell wrote:
> > Until someone fixes all the places in the kernel where scheduling can
> > be held off for tens of milliseconds, CONFIG_PREEMPT will be an
> > absolute requirement for many applications like audio and gaming.
>
> There's nothing wrong with CONFIG_PREEMPT for those users. We have
> a few other performance concessions activated with CONFIG_PREEMPT on.
> I think a usual upper of a few miliseconds (especially for SMP) is
> reasonable for a non preempt kernel.

This is within reach - the only major offender left is
rt_secret_rebuild (and possibly other areas of the route cache
handling).  Eric Dumazet had some suggestions to fix it, but the
details are beyond my area of expertise.

Lee
-
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/