From: Daniel Baluta <dbaluta@ixiacom.com>
To: greg@kroah.com, linux-kernel@vger.kernel.org
Cc: marek.belisko@gmail.com, Daniel Baluta <dbaluta@ixiacom.com>
Subject: [PATCH] kref: add function for reading kref value
Date: Mon, 12 Dec 2011 15:41:48 +0200 [thread overview]
Message-ID: <1323697308-25121-1-git-send-email-dbaluta@ixiacom.com> (raw)
In-Reply-To: <1323693892-11570-1-git-send-email-dbaluta@ixiacom.com>
We can easily get kref refcount value by accesing
kref->refcount but it is better to have a function
for this.
Signed-off-by: Daniel Baluta <dbaluta@ixiacom.com>
---
include/linux/kref.h | 1 +
lib/kref.c | 9 +++++++++
2 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/include/linux/kref.h b/include/linux/kref.h
index d4a62ab..f2e69c1 100644
--- a/include/linux/kref.h
+++ b/include/linux/kref.h
@@ -22,6 +22,7 @@ struct kref {
};
void kref_init(struct kref *kref);
+int kref_read(struct kref *kref);
void kref_get(struct kref *kref);
int kref_put(struct kref *kref, void (*release) (struct kref *kref));
int kref_sub(struct kref *kref, unsigned int count,
diff --git a/lib/kref.c b/lib/kref.c
index 3efb882..fc7be37 100644
--- a/lib/kref.c
+++ b/lib/kref.c
@@ -26,6 +26,15 @@ void kref_init(struct kref *kref)
}
/**
+ * kref_read - read refcount for object
+ * @kref: object.
+ */
+int kref_read(struct kref *kref)
+{
+ return atomic_read(&kref->refcount);
+}
+
+/**
* kref_get - increment refcount for object.
* @kref: object.
*/
--
1.7.1
next prev parent reply other threads:[~2011-12-12 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 12:44 Daniel Baluta
2011-12-12 12:51 ` Belisko Marek
2011-12-12 12:55 ` Daniel Baluta
2011-12-12 13:41 ` Daniel Baluta [this message]
2011-12-12 15:09 ` Alexey Dobriyan
2011-12-12 15:02 ` Greg KH
2011-12-12 15:21 ` Daniel Baluta
2011-12-12 15:32 ` Eric Dumazet
2011-12-12 15:39 ` Daniel Baluta
2011-12-12 15:41 ` Eric Dumazet
2011-12-12 16:42 ` Daniel Baluta
2011-12-12 17:33 ` Greg KH
2011-12-12 17:46 ` Daniel Baluta
2011-12-12 17:57 ` Eric Dumazet
2011-12-12 18:33 ` Greg KH
2011-12-12 17:42 ` Eric Dumazet
2011-12-12 15:28 ` Peter Zijlstra
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=1323697308-25121-1-git-send-email-dbaluta@ixiacom.com \
--to=dbaluta@ixiacom.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.belisko@gmail.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
all inboxes | Powered by JetHome®