From: Byungchul Park <byungchul.park@lge.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: peterz@infradead.org, mingo@kernel.org, neilb@suse.de,
nab@linux-iscsi.org, viro@zeniv.linux.org.uk, oleg@redhat.com,
shli@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each
Date: Mon, 13 Feb 2017 16:58:05 +0900 [thread overview]
Message-ID: <20170213075805.GL16086@X58A-UD3R> (raw)
In-Reply-To: <87y3xao7cj.fsf@yhuang-dev.intel.com>
On Mon, Feb 13, 2017 at 03:52:44PM +0800, Huang, Ying wrote:
> Byungchul Park <byungchul.park@lge.com> writes:
>
> > On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying wrote:
> >> Byungchul Park <byungchul.park@lge.com> writes:
> >>
> >> > Sometimes we have to dereference next field of llist node before entering
> >> > loop becasue the node might be deleted or the next field might be
> >> > modified within the loop. So this adds the safe version of llist_for_each,
> >> > that is, llist_for_each_safe.
> >> >
> >> > Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> >> > ---
> >> > include/linux/llist.h | 19 +++++++++++++++++++
> >> > 1 file changed, 19 insertions(+)
> >> >
> >> > diff --git a/include/linux/llist.h b/include/linux/llist.h
> >> > index fd4ca0b..4c508a5 100644
> >> > --- a/include/linux/llist.h
> >> > +++ b/include/linux/llist.h
> >> > @@ -105,6 +105,25 @@ static inline void init_llist_head(struct llist_head *list)
> >> > for ((pos) = (node); pos; (pos) = (pos)->next)
> >> >
> >> > /**
> >> > + * llist_for_each_safe - iterate over some deleted entries of a lock-less list
> >> > + * safe against removal of list entry
> >> > + * @pos: the &struct llist_node to use as a loop cursor
> >> > + * @n: another type * to use as temporary storage
> >>
> >> s/type */&struct llist_node/
> >
> > Yes.
> >
> >>
> >> > + * @node: the first entry of deleted list entries
> >> > + *
> >> > + * In general, some entries of the lock-less list can be traversed
> >> > + * safely only after being deleted 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.
> >> > + */
> >> > +#define llist_for_each_safe(pos, n, node) \
> >> > + for ((pos) = (node); (pos) && ((n) = (pos)->next, true); (pos) = (n))
> >> > +
> >>
> >> Following the style of other xxx_for_each_safe,
> >>
> >> #define llist_for_each_safe(pos, n, node) \
> >> for (pos = (node), (pos && (n = pos->next)); pos; pos = n, n = pos->next)
> >
> > Do you think it should be modified? I think mine is simpler. No?
>
> Personally I prefer the style of other xxx_for_each_safe().
Yes, I will modify it as you recommand.
Thank you very much.
>
> Best Regards,
> Huang, Ying
>
> >>
> >> Best Regards,
> >> Huang, Ying
> >>
> >> > +/**
> >> > * llist_for_each_entry - iterate over some deleted entries of lock-less list of given type
> >> > * @pos: the type * to use as a loop cursor.
> >> > * @node: the fist entry of deleted list entries.
next prev parent reply other threads:[~2017-02-13 7:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 7:21 [PATCH v2 0/9] Don't reinvent the wheel but use existing llist API Byungchul Park
2017-02-13 7:21 ` [PATCH v2 1/9] llist: Provide a safe version for llist_for_each Byungchul Park
2017-02-13 7:36 ` Huang, Ying
2017-02-13 7:44 ` Byungchul Park
2017-02-13 7:52 ` Huang, Ying
2017-02-13 7:58 ` Byungchul Park [this message]
2017-02-14 6:44 ` Byungchul Park
2017-02-14 6:59 ` Huang, Ying
2017-02-13 7:21 ` [PATCH v2 2/9] bcache: Don't reinvent the wheel but use existing llist API Byungchul Park
2017-02-13 7:21 ` [PATCH v2 3/9] raid5: " Byungchul Park
2017-02-13 7:21 ` [PATCH v2 4/9] vhost/scsi: " Byungchul Park
2017-02-13 7:21 ` [PATCH v2 5/9] fput: " Byungchul Park
2017-02-13 7:21 ` [PATCH v2 6/9] namespace.c: " Byungchul Park
2017-02-13 7:21 ` [PATCH v2 7/9] irq_work: " Byungchul Park
2017-02-13 7:21 ` [PATCH v2 8/9] sched: " Byungchul Park
2017-02-13 10:04 ` Peter Zijlstra
2017-02-13 15:52 ` Oleg Nesterov
2017-02-13 23:00 ` Byungchul Park
2017-02-13 22:59 ` Byungchul Park
2017-02-13 7:21 ` [PATCH v2 9/9] mm: " Byungchul Park
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=20170213075805.GL16086@X58A-UD3R \
--to=byungchul.park@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nab@linux-iscsi.org \
--cc=neilb@suse.de \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=shli@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=ying.huang@intel.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
Powered by JetHome