From: Anton Blanchard <anton@samba.org>
To: linas@austin.ibm.com
Cc: linux-kernel@vger.kernel.org, davem@redhat.com, mingo@redhat.com,
riel@redhat.com, mranweil@us.ibm.com
Subject: Re: PATCH: kernel-2.4 brlock livelock
Date: Thu, 4 Sep 2003 05:44:02 +1000 [thread overview]
Message-ID: <20030903194401.GA688@krispykreme> (raw)
In-Reply-To: <20030903142150.A48064@forte.austin.ibm.com>
Hi,
> The patch changes the non-atomic code. It grabs the write lock, and
> then spins, waiting for all of the existing readers to finish.
> New readers are held off. This seems (to me) to be a reasonable
> thing to do, based on the following logic:
The problem is with recursive readers. One cpu takes a br read lock then
wants to take the same lock again. It must be allowed to get that read lock.
We need to drop the write spinlock or else we will deadlock.
Anton
next prev parent reply other threads:[~2003-09-03 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 19:21 PATCH: kernel-2.4 brlock livelock linas
2003-09-03 19:44 ` Anton Blanchard [this message]
2003-09-03 20:10 ` linas
2003-09-04 8:59 ` 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=20030903194401.GA688@krispykreme \
--to=anton@samba.org \
--cc=davem@redhat.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mranweil@us.ibm.com \
--cc=riel@redhat.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