All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David C. Hansen" <haveblue@us.ibm.com>
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 13:10:13 -0800	[thread overview]
Message-ID: <3C586135.2020304@us.ibm.com> (raw)
In-Reply-To: <20020130184950.GA22442@morgoth.mit.edu> <1012418760.3219.43.camel@phantasy>

Robert Love wrote:

>On Wed, 2002-01-30 at 13:49, Alex Khripin wrote:
>
>>I'm very much a newbie, and I'm wondering about the big kernel locks
>>in tty_io.c. What exactly are the locks in the read and write for? Is the
>>tty device that contested? Couldn't a finer grained lock be used?
>>
>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.
>
People working on BKL removal tend to ignore these types of things (I 
know I do).  We concentrate on scalability and performance and the tty 
code isn't exactly a high point of lock contention.



  parent reply	other threads:[~2002-01-30 21:10 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
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 [this message]
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=3C586135.2020304@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.