In order to assign the result from list_prepare_entry() to another
variable, it should also be set when pos != NULL.
This will be useful once the list iterator is no longer used after
the loop.
The original code:
list_for_each_entry(fl, head, list) {
if (...)
break;
}
list_for_each_entry_continue(fl, head, list) {
}
can then just be turned into something like this:
list_for_each_entry(fl, head, list) {
if (...) {
tmp = fl;
break;
}
}
fl = list_prepare_entry(tmp, head, list);
list_for_each_entry_continue(fl, head, list) {
}
The compiler should happily optimize away the
TRUE case if the variable being assigned is the same:
pos = list_prepare_entry(pos, head, list);
and only do it in the case where the variable to assign
is different:
pos = list_prepare_entry(tmp, head, list);
Signed-off-by: Jakob Koschel <[email protected]>
---
include/linux/list.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/list.h b/include/linux/list.h
index dd6c2041d09c..050747fb5ea8 100644
--- a/include/linux/list.h
+++ b/include/linux/list.h
@@ -659,7 +659,7 @@ static inline void list_splice_tail_init(struct list_head *list,
* Prepares a pos entry for use as a start point in list_for_each_entry_continue().
*/
#define list_prepare_entry(pos, head, member) \
- ((pos) ? : list_entry(head, typeof(*pos), member))
+ ((pos) ? pos : list_entry(head, typeof(*pos), member))
/**
* list_for_each_entry_continue - continue iteration over list of given type
base-commit: 719fce7539cd3e186598e2aed36325fe892150cf
--
2.25.1
> On 7. Mar 2022, at 10:49, Andy Shevchenko <[email protected]> wrote:
>
> On Sun, Mar 06, 2022 at 05:26:35PM +0100, Jakob Koschel wrote:
>> In order to assign the result from list_prepare_entry() to another
>> variable, it should also be set when pos != NULL.
>>
>> This will be useful once the list iterator is no longer used after
>> the loop.
>
> ...
>
>> #define list_prepare_entry(pos, head, member) \
>> - ((pos) ? : list_entry(head, typeof(*pos), member))
>> + ((pos) ? pos : list_entry(head, typeof(*pos), member))
>
> I'm not sure why then we have () surrounding first pos.
>
> Am I right that the original is an equivalent to
>
> ((pos) ? (pos) : list_entry(head, typeof(*pos), member))
>
> ?
Yes you are right.
I've just tested this again and seems like my local setup was skewed.
My assumption (from some coccinelle output) was that leaving the TRUE case
empty will not do any assignment at all but that's obviously wrong and I
can't reproduce it.
Basically feel free to ignore this PATCH since it just seems to be a NO-OP.
>
> Then what the difference is made by not using parentheses?
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
Jakob
On Sun, Mar 06, 2022 at 05:26:35PM +0100, Jakob Koschel wrote:
> In order to assign the result from list_prepare_entry() to another
> variable, it should also be set when pos != NULL.
>
> This will be useful once the list iterator is no longer used after
> the loop.
...
> #define list_prepare_entry(pos, head, member) \
> - ((pos) ? : list_entry(head, typeof(*pos), member))
> + ((pos) ? pos : list_entry(head, typeof(*pos), member))
I'm not sure why then we have () surrounding first pos.
Am I right that the original is an equivalent to
((pos) ? (pos) : list_entry(head, typeof(*pos), member))
?
Then what the difference is made by not using parentheses?
--
With Best Regards,
Andy Shevchenko