From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@infradead.org>,
Ravikiran G Thirumalai <kiran@in.ibm.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] Add kref_read and kref_put_last primitives
Date: Mon, 2 Aug 2004 13:08:49 -0700 [thread overview]
Message-ID: <20040802200849.GG28374@kroah.com> (raw)
In-Reply-To: <20040726173151.A11637@infradead.org>
On Mon, Jul 26, 2004 at 05:31:51PM +0100, Christoph Hellwig wrote:
> On Mon, Jul 26, 2004 at 08:18:56PM +0530, Ravikiran G Thirumalai wrote:
> > Greg,
> > Here is a patch to add kref_read and kref_put_last.
> > These primitives were needed to change files_struct.f_count
> > refcounter to use kref api.
> >
> > kref_put_last is needed sometimes when a refcount might
> > have an unconventional release which needs more than
> > the refcounted object to process object release-- like in the
> > files_struct.f_count conversion patch at __aio_put_req().
> > The following patch depends on kref shrinkage patches.
> > (which you have already included).
>
> Why don't you simply use an atomic_t if that's what you seem to
> want?
Exactly. In cases like this, where the user, for some reason, wants to
know the state of the reference count, they should not use a struct
kref. I'm not going to add these functions to the kref api, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2004-08-02 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 14:48 [patch] Add kref_read and kref_put_last primitives Ravikiran G Thirumalai
2004-07-26 14:56 ` Ravikiran G Thirumalai
2004-07-26 16:31 ` Christoph Hellwig
2004-07-27 7:09 ` Ravikiran G Thirumalai
2004-07-27 9:43 ` Christoph Hellwig
2004-08-02 20:08 ` Greg KH [this message]
2004-08-03 5:42 ` Dipankar Sarma
2004-08-03 6:51 ` Greg KH
2004-08-03 7:45 ` Dipankar Sarma
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=20040802200849.GG28374@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=kiran@in.ibm.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