Date: Sun, 23 Jan 2005 12:31:11 +0100
From: Ingo Molnar <mingo@elte.hu>
To: andyliu <liudeyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.11-rc2-V0.7.36-00
Message-ID: <20050123113111.GA11965@elte.hu>
References: <20041122005411.GA19363@elte.hu> <20050115133454.GA8748@elte.hu> <20050122122915.GA7098@elte.hu> <200501221622.24273.gene.heskett@verizon.net> <aad1205e05012301271de3e365@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aad1205e05012301271de3e365@mail.gmail.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1240
Lines: 30


* andyliu <liudeyan@gmail.com> wrote:

> hi , ingo
> 
> i am trying to understand your patch,but the patch file is so long and
> complex. i am wondering is there some documents about your patch?
> 
> :)

well, it mainly offers the PREEMPT_RT feature, which is a 'no
compromises' variant of kernel preemption: virtually everything
(including normal spinlocked sections) is preemptable, with the goal of
providing hard-realtime category ~10-20 usecs maximum scheduling latency
guarantees on a typical PC (or embedded platform). Those long and
complex changes are almost all needed to achieve this goal.

this tree is mainly an experiment to see what it takes to achieve that
latency goal, and to see how much of that can go upstream (without
having to decide whether upstream wants to have the PREEMPT_RT feature
or not). (A couple of dozen patches were already split out of this patch
and are in the current upstream kernel - they already made a latency
difference for the 2.6.10 kernel.)

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