From: "David S. Miller" <davem@redhat.com>
To: rmk@arm.linux.org.uk
Cc: mingo@elte.hu, torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] O(1) scheduler, -H5
Date: Fri, 11 Jan 2002 04:05:37 -0800 (PST) [thread overview]
Message-ID: <20020111.040537.115909086.davem@redhat.com> (raw)
In-Reply-To: <20020111113131.C30756@flint.arm.linux.org.uk>
In-Reply-To: <Pine.LNX.4.33.0201110130290.11478-100000@localhost.localdomain> <20020111113131.C30756@flint.arm.linux.org.uk>
From: Russell King <rmk@arm.linux.org.uk>
Date: Fri, 11 Jan 2002 11:31:31 +0000
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.
The tty layer is really the only layer that hasn't had any
"SMP love and care" given to it.
Last time I looked at trying to do something it appeared you could fix
the whole thing up with a semaphore for the user bits and a spinlock
with which to interlock with the drivers.
next prev parent reply other threads:[~2002-01-11 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 0:38 [patch] O(1) scheduler, -H5 Ingo Molnar
2002-01-11 11:31 ` Russell King
2002-01-11 12:05 ` David S. Miller [this message]
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
[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
2002-01-11 11:57 ` 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
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=20020111.040537.115909086.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@transmeta.com \
/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