From: Andi Kleen <ak@suse.de>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] O(1) scheduler, -H5
Date: 11 Jan 2002 12:42:14 +0100 [thread overview]
Message-ID: <p73zo3lnmg9.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0201110130290.11478-100000@localhost.localdomain.suse.lists.linux.kernel> <20020111113131.C30756@flint.arm.linux.org.uk.suse.lists.linux.kernel>
In-Reply-To: Russell King's message of "11 Jan 2002 12:37:44 +0100"
Russell King <rmk@arm.linux.org.uk> writes:
>
> The serial driver (old or new) open/close functions are one of the worst
> offenders of the global-cli-and-hold-kernel-lock-and-schedule problem.
> I'm currently working on fixing this in the new serial driver.
When they hold the kernel lock in addition to the global cli() before
schedule() it should be ok. Only the behaviour of code not holding
kernel lock but global cli and calling schedule() has changed.
-Andi
next parent reply other threads:[~2002-01-11 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0201110130290.11478-100000@localhost.localdomain.suse.lists.linux.kernel>
[not found] ` <20020111113131.C30756@flint.arm.linux.org.uk.suse.lists.linux.kernel>
2002-01-11 11:42 ` Andi Kleen [this message]
2002-01-11 11:57 ` [patch] O(1) scheduler, -H5 Russell King
2002-01-11 12:00 ` Arjan van de Ven
[not found] <20020111091744.B1170@w-mikek2.des.beaverton.ibm.com>
2002-01-13 17:18 ` Ingo Molnar
2002-01-11 0:38 Ingo Molnar
2002-01-11 11:31 ` Russell King
2002-01-11 12:05 ` David S. Miller
2002-01-11 13:09 ` Alan Cox
2002-01-11 14:58 ` Russell King
2002-01-11 15:22 ` Alan Cox
2002-01-11 15:23 ` Russell King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p73zo3lnmg9.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox