From: zwu.kernel@gmail.com
To: viro@zeniv.linux.org.uk
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-btrfs@vger.kernel.org, sekharan@us.ibm.com,
linuxram@us.ibm.com, david@fromorbit.com, dsterba@suse.cz,
gregkh@linuxfoundation.org, paulmck@linux.vnet.ibm.com,
chris.mason@fusionio.com, Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
Subject: [PATCH v2 05/12] VFS hot tracking, rcu: introduce one rcu macro for list
Date: Tue, 14 May 2013 08:59:37 +0800 [thread overview]
Message-ID: <1368493184-5939-6-git-send-email-zwu.kernel@gmail.com> (raw)
In-Reply-To: <1368493184-5939-1-git-send-email-zwu.kernel@gmail.com>
From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
This rcu macro for list will be used in seq_list
rcu interfaces.
Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>
Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
---
include/linux/rculist.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/linux/rculist.h b/include/linux/rculist.h
index 8089e35..a3fa055 100644
--- a/include/linux/rculist.h
+++ b/include/linux/rculist.h
@@ -218,6 +218,11 @@ static inline void list_splice_init_rcu(struct list_head *list,
at->prev = last;
}
+#define __list_for_each_rcu(pos, head) \
+ for (pos = rcu_dereference(list_next_rcu(head)); \
+ pos != head; \
+ pos = rcu_dereference(list_next_rcu(pos)))
+
/**
* list_entry_rcu - get the struct for this entry
* @ptr: the &struct list_head pointer.
--
1.7.11.7
next prev parent reply other threads:[~2013-05-14 0:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 0:59 [PATCH v2 00/12] VFS hot tracking zwu.kernel
2013-05-14 0:59 ` [PATCH v2 01/12] VFS hot tracking: introduce some data structures zwu.kernel
2013-05-14 0:59 ` [PATCH v2 02/12] VFS hot tracking: add i/o freq tracking hooks zwu.kernel
2013-05-14 0:59 ` [PATCH v2 03/12] VFS hot tracking: add one workqueue to update hot map zwu.kernel
2013-05-14 0:59 ` [PATCH v2 04/12] VFS hot tracking: register one shrinker zwu.kernel
2013-05-14 0:59 ` zwu.kernel [this message]
2013-05-14 0:59 ` [PATCH v2 06/12] VFS hot tracking, seq_file: introduce one set of rcu seq_list interfaces zwu.kernel
2013-05-14 0:59 ` [PATCH v2 07/12] VFS hot tracking: add debugfs support zwu.kernel
2013-05-14 0:59 ` [PATCH v2 08/12] VFS hot tracking: add one ioctl interface zwu.kernel
2013-05-14 0:59 ` [PATCH v2 09/12] VFS hot tracking, procfs: add two proc interfaces zwu.kernel
2013-05-14 0:59 ` [PATCH v2 10/12] VFS hot tracking, btrfs: add hot tracking support zwu.kernel
2013-05-14 0:59 ` [PATCH v2 11/12] VFS hot tracking: add documentation zwu.kernel
2013-05-14 0:59 ` [PATCH v2 12/12] VFS hot tracking: add fs hot type support zwu.kernel
2013-05-21 22:55 ` [PATCH v2 00/12] VFS hot tracking Zhi Yong Wu
2013-05-24 3:39 ` Zhi Yong Wu
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=1368493184-5939-6-git-send-email-zwu.kernel@gmail.com \
--to=zwu.kernel@gmail.com \
--cc=chris.mason@fusionio.com \
--cc=david@fromorbit.com \
--cc=dsterba@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sekharan@us.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wuzhy@linux.vnet.ibm.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).