From: Huang Ying <ying.huang@intel.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: linux-kernel@vger.kernel.org, Konrad Rzeszutek Wilk <konrad@kernel.org>
Subject: Re: [PATCH v4 2/3] llist: add a safe version of llist_for_each_entry
Date: Fri, 14 Dec 2012 08:53:29 +0800 [thread overview]
Message-ID: <1355446409.24876.110.camel@yhuang-dev> (raw)
In-Reply-To: <1355395179-55724-2-git-send-email-roger.pau@citrix.com>
On Thu, 2012-12-13 at 11:39 +0100, Roger Pau Monne wrote:
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> Cc: Huang Ying <ying.huang@intel.com>
> Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>
Reviewed-by: Huang Ying <ying.huang@intel.com>
> ---
> Changes since v3:
> * Change n to use type *, to keep the same semantics as
> list_for_each_entry_safe.
> Changes since v2:
> * Allow to pass a NULL node as the first entry of deleted list
> entries.
> ---
> include/linux/llist.h | 29 +++++++++++++++++++++++++++++
> 1 files changed, 29 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/llist.h b/include/linux/llist.h
> index a5199f6..f551ac4 100644
> --- a/include/linux/llist.h
> +++ b/include/linux/llist.h
> @@ -125,6 +125,35 @@ static inline void init_llist_head(struct llist_head *list)
> (pos) = llist_entry((pos)->member.next, typeof(*(pos)), member))
>
> /**
> + * llist_for_each_entry_safe - safely iterate over some deleted entries of
> + * lock-less list of given type
> + * @pos: the type * to use as a loop cursor.
> + * @n: another type * to use as temporary storage
> + * @node: the fist entry of deleted list entries.
> + * @member: the name of the llist_node with the struct.
> + *
> + * In general, some entries of the lock-less list can be traversed
> + * safely only after being removed from list, so start with an entry
> + * instead of list head.
> + *
> + * If being used on entries deleted from lock-less list directly, the
> + * traverse order is from the newest to the oldest added entry. If
> + * you want to traverse from the oldest to the newest, you must
> + * reverse the order by yourself before traversing.
> + *
> + * n is used to store a reference to the next item llist_node, so
> + * pos can be freed while iterating.
> + */
> +#define llist_for_each_entry_safe(pos, n, node, member) \
> + for ((pos) = llist_entry((node), typeof(*(pos)), member), \
> + (n) = llist_entry(((&(pos)->member != NULL) ? \
> + (pos)->member.next : NULL), typeof(*(pos)), member); \
> + &(pos)->member != NULL; \
> + (pos) = n, \
> + (n) = llist_entry(((&(pos)->member != NULL) ? \
> + (pos)->member.next : NULL), typeof(*(pos)), member))
> +
> +/**
> * llist_empty - tests whether a lock-less list is empty
> * @head: the list to test
> *
next prev parent reply other threads:[~2012-12-14 0:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 10:39 [PATCH v4 1/3] xen-blkback: implement safe iterator for the list of persistent grants Roger Pau Monne
2012-12-13 10:39 ` [PATCH v4 2/3] llist: add a safe version of llist_for_each_entry Roger Pau Monne
2012-12-14 0:53 ` Huang Ying [this message]
2012-12-13 10:39 ` [PATCH v4 3/3] xen-blkfront: transverse list of persistent grants safely Roger Pau Monne
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=1355446409.24876.110.camel@yhuang-dev \
--to=ying.huang@intel.com \
--cc=konrad@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.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