From: Manfred Spraul <manfred@colorfullife.com>
To: andrewm@uow.edu.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: [prepatches] removal of console_lock
Date: Sun, 04 Mar 2001 11:57:41 +0100 [thread overview]
Message-ID: <3AA21FA5.BA370402@colorfullife.com> (raw)
> - Major revamp of printk(). The approach taken in printk() is to try
> to acquire the (new) console_sem. If we succeed, the output is
> placed into the log buffer and is printed to the consoles. If we fail
> to acquire the semaphore we just buffer the output in the log buffer
> and the current holder of the console_sem will do the printing for us
> prior to releasing console_sem.
Is down_trylock reliable under load?
I remember 2 or 3 bug reports than disappeared after down_trylock was
removed.
The last one was this week.
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg31919.html
--
Manfred
next reply other threads:[~2001-03-04 10:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-04 10:57 Manfred Spraul [this message]
2001-03-04 11:19 ` [prepatches] removal of console_lock Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2001-03-04 7:31 Andrew Morton
2001-03-04 10:26 ` Pierre Rousselet
2001-03-04 10:42 ` Andrew Morton
2001-03-05 6:15 ` Cort Dougan
2001-03-05 13:00 ` Andrew Morton
2001-03-05 14:36 ` Benjamin Herrenschmidt
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=3AA21FA5.BA370402@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
/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