From: Peter Zijlstra <peterz@infradead.org>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: Q: (stupid) can't we "fix" hlist_for_each_entry() ?
Date: Wed, 12 Mar 2008 10:48:50 +0100 [thread overview]
Message-ID: <1205315331.8514.225.camel@twins> (raw)
In-Reply-To: <20080312081201.GA278@tv-sign.ru>
On Wed, 2008-03-12 at 11:12 +0300, Oleg Nesterov wrote:
> hlist_for_each_entry/hlist_for_each_entry_rcu doesn't actually need 4
> arguments, it could be
>
> #define hlist_for_each_entry_rcu(pos, head, member) \
> for (pos = hlist_entry((head)->first, typeof(*(pos)), member); \
> rcu_dereference(pos) != hlist_entry(NULL, typeof(*(pos)), member) && \
> ({ prefetch((pos)->member.next); 1; }); \
> (pos) = hlist_entry((pos)->member.next, typeof(*(pos)), member))
>
> Or,
>
> #define hlist_for_each_entry_rcu(pos, head, member) \
> for (pos = (void*)(head)->first; \
> rcu_dereference(pos) && ({ prefetch(((hlist_node*)pos)->next); 1; }) && \
> ({ (pos) = hlist_entry((void*)(pos), typeof(*(pos)), member)); 1; }); \
> (pos) = (void*)(pos)->member.next)
>
> Q: is it worth "fixing" ?
I'm in favour.
> If yes, what is the "right" way to do this? These macros are spread all over
> the kernel...
The usual way would be to prepare a git tree for Linus to pull right
after -rc1 I think was the best point, and at the same time supply
Andrew with a bunch of patches fixing up the various users in his tree.
next prev parent reply other threads:[~2008-03-12 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 8:12 Q: (stupid) can't we "fix" hlist_for_each_entry() ? Oleg Nesterov
2008-03-12 9:48 ` Peter Zijlstra [this message]
2008-03-12 17:27 ` Andrew Morton
2008-03-12 12:53 ` Paul E. McKenney
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=1205315331.8514.225.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=paulmck@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