public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Liu Tao <liutao@safe-mail.net>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: arjanv@redhat.com, lkml <linux-kernel@vger.kernel.org>,
	Oliver Neukum <oliver@neukum.org>
Subject: Re: [patch] Add a writer prior lock methord for rwlock
Date: Wed, 04 Aug 2004 19:30:19 +0800	[thread overview]
Message-ID: <4110C8CB.1030108@safe-mail.net> (raw)
In-Reply-To: <20040804103337.GN2334@holomorphy.com>

William Lee Irwin III wrote:

>Unfortunately this will deadlock. read locks are acquired recursively.
>The algorithms dependent on this need to be redesigned.
>
>  
>

Thanks, it's not a feasible scheme since read locks are recursive.

Regards

  reply	other threads:[~2004-08-04 11:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04  9:09 [patch] Add a writer prior lock methord for rwlock Liu Tao
2004-08-04  9:16 ` Arjan van de Ven
2004-08-04 10:29   ` Liu Tao
2004-08-04 10:33     ` William Lee Irwin III
2004-08-04 11:30       ` Liu Tao [this message]
2004-08-04 12:14     ` Rik van Riel
2004-08-04  9:45 ` Oliver Neukum
2004-08-04 10:30   ` Liu Tao

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=4110C8CB.1030108@safe-mail.net \
    --to=liutao@safe-mail.net \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=wli@holomorphy.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