From: Russell King <rmk@arm.linux.org.uk>
To: Robert Love <rml@tech9.net>
Cc: Alex Khripin <akhripin@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: BKL in tty code?
Date: Wed, 30 Jan 2002 21:01:27 +0000 [thread overview]
Message-ID: <20020130210127.H19292@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20020130184950.GA22442@morgoth.mit.edu> <1012418760.3219.43.camel@phantasy>
In-Reply-To: <1012418760.3219.43.camel@phantasy>; from rml@tech9.net on Wed, Jan 30, 2002 at 02:25:59PM -0500
On Wed, Jan 30, 2002 at 02:25:59PM -0500, Robert Love wrote:
> It has less to do with lock contention and much more to do with the
> design of the tty / console layer. It isn't the kernel's prettiest
> code.
>
> There is probably some cleanup that is possible, but really getting the
> thing in gear (which means no BKL, which is probably the hardest part to
> rip out) require some level of rewrite.
I've been thinking about the serial layer, and its far from trivial.
Unless its done right, we'll end up with a mess of locks -> deadlock.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-01-30 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 18:49 BKL in tty code? Alex Khripin
2002-01-30 19:25 ` Robert Love
2002-01-30 21:01 ` Russell King [this message]
2002-01-30 22:58 ` James Simmons
2002-01-30 23:05 ` Russell King
2002-01-30 22:52 ` Karl
2002-01-30 23:14 ` James Simmons
2002-01-30 21:10 ` David C. Hansen
2002-01-30 21:57 ` Karl
2002-01-30 23:00 ` James Simmons
2002-01-30 22:57 ` James Simmons
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=20020130210127.H19292@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akhripin@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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