From: Rusty Russell <rusty@rustcorp.com.au>
To: Kedar Sovani <kedars@gmail.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Unreliable Guide to Locking - Addition?
Date: Tue, 09 Aug 2005 12:35:06 +1000 [thread overview]
Message-ID: <1123554907.13481.20.camel@localhost.localdomain> (raw)
In-Reply-To: <5edf7fc905080806117df1ab32@mail.gmail.com>
On Mon, 2005-08-08 at 18:41 +0530, Kedar Sovani wrote:
> when the last atomic_dec_and_test() (the last == the one which
> returns 0) is being called on the object, the object is usually not
> accessible to others (list_del()) and hence the simultaneous
> atomic_inc() call never occurs.
Yes, a reference count must count references. Of course, you can get
around with with "atomic_dec_and_lock", but I hate that primitive as it
has scalability issues (it can't be translated to RCU).
I'll look and see if I can make this requirement explicit.
Thanks!
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
prev parent reply other threads:[~2005-08-09 2:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 13:11 Unreliable Guide to Locking - Addition? Kedar Sovani
2005-08-09 2:35 ` Rusty Russell [this message]
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=1123554907.13481.20.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=kedars@gmail.com \
--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