Message-ID: <20031108012755.41882.qmail@web80007.mail.yahoo.com>
Date: Fri, 7 Nov 2003 17:27:55 -0800 (PST)
From: Oleg OREL <oleg_orel@yahoo.com>
Reply-To: oleg_orel@yahoo.com
Subject: Linux kernel preemption (kernel 2.6 of course)
To: linux-kernel@vger.kernel.org
In-Reply-To: <20031108003029.BF9DB5F711@attila.bofh.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 814
Lines: 24


I was browsing linux kernel to undetsnand how kernel preemption does
work. I was hacking around schedulee_tick and other functions called
out of timer interrupt and was unable to found any call to schedule()
or switch_to() to peempt currently running task, instead just mangling
around current and inactive runqueues.

That leads me to a thought that currently running task wont be
preempted within time-tick, instead it might happends in the next call
to preempt_schedule out of spin_lock for instance.
 

=====
Oleg OREL

TEL: +1 925 244-1127
CELL: +1 916 337-0608
-
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/