From: David Howells <dhowells@cambridge.redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
William Lee Irwin III <wli@holomorphy.com>,
"Van Maren, Kevin" <kevin.vanmaren@unisys.com>,
linux-ia64@linuxia64.org,
Linux Kernel List <linux-kernel@vger.kernel.org>,
rusty@rustcorp.com.au, dhowells@redhat.com, mingo@elte.hu
Subject: Re: [Linux-ia64] reader-writer livelock problem
Date: Fri, 08 Nov 2002 17:43:35 +0000 [thread overview]
Message-ID: <18932.1036777415@warthog.cambridge.redhat.com> (raw)
In-Reply-To: Message from Jeremy Fitzhardinge <jeremy@goop.org> of "08 Nov 2002 09:38:25 PST." <1036777105.13021.13.camel@ixodes.goop.org>
> Do you mean have a separate lock type, or have two different read_lock
> operations on the current type?
You'd probably be better off with separate types... that way you can avoid
problems with conditionals and also with different tracking fields being
required by each grade of lock.
David
next prev parent reply other threads:[~2002-11-08 17:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3FAD1088D4556046AEC48D80B47B478C0101F4E7@usslc-exch-4.slc.unisys.com>
2002-11-08 3:51 ` [Linux-ia64] reader-writer livelock problem William Lee Irwin III
2002-11-08 17:13 ` Jeremy Fitzhardinge
2002-11-08 17:25 ` Linus Torvalds
2002-11-08 17:28 ` Linus Torvalds
2002-11-08 17:38 ` Jeremy Fitzhardinge
2002-11-08 17:43 ` David Howells [this message]
2002-11-08 17:57 ` Linus Torvalds
2002-11-09 2:48 ` Rusty Russell
2002-11-09 4:36 ` William Lee Irwin III
[not found] ` <3DCFDAE9.6D359448@email.mot.com>
2002-11-11 19:22 ` David Mosberger
2002-11-12 1:39 ` your mail Rik van Riel
2002-11-08 17:34 ` [Linux-ia64] reader-writer livelock problem David Howells
2002-11-08 17:54 ` David Howells
2002-11-08 17:55 ` Stephen Hemminger
2002-11-08 17:41 Van Maren, Kevin
2002-11-08 17:52 ` Matthew Wilcox
2002-11-08 18:05 Van Maren, Kevin
2002-11-08 19:19 ` Matthew Wilcox
2002-11-08 19:26 ` David Mosberger
2002-11-08 20:17 Van Maren, Kevin
2002-11-08 20:39 ` Matthew Wilcox
2002-11-08 20:24 Van Maren, Kevin
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=18932.1036777415@warthog.cambridge.redhat.com \
--to=dhowells@cambridge.redhat.com \
--cc=dhowells@redhat.com \
--cc=jeremy@goop.org \
--cc=kevin.vanmaren@unisys.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
--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;
as well as URLs for NNTP newsgroup(s).