On Wed, Dec 06, 2023 at 05:05:30PM +1100, Dave Chinner wrote:

> +static inline struct dlock_list_node *
> +__dlock_list_next_entry(struct dlock_list_node *curr,
> +                     struct dlock_list_iter *iter)
> +{
> +     /*
> +      * Find next entry
> +      */
> +     if (curr)
> +             curr = list_next_entry(curr, list);
> +
> +     if (!curr || (&curr->list == &iter->entry->list)) {

Hmm...  hlist, perhaps?  I mean, that way the thing becomes
        if (curr)
                curr = hlist_entry_safe(curr->node.next,
                                        struct dlock_list_node, node);
        if (!curr)
                curr = __dlock_list_next_list(iter);
        return curr;

BTW, does anybody have objections against

#define hlist_first_entry(head, type, member)
        hlist_entry_safe((head)->first, type, member)

#define hlist_next_entry(pos, member)
        hlist_entry_safe((pos)->member.next, typeof(*pos), member)

added in list.h?

> +static int __init cpu2idx_init(void)
> +{
> +     int idx, cpu;
> +
> +     idx = 0;
> +     for_each_possible_cpu(cpu)
> +             per_cpu(cpu2idx, cpu) = idx++;
> +     return 0;
> +}
> +postcore_initcall(cpu2idx_init);

Is it early enough?  Feels like that ought to be done from smp_init() or
right after it...

> +/**
> + * dlock_lists_empty - Check if all the dlock lists are empty
> + * @dlist: Pointer to the dlock_list_heads structure
> + * Return: true if list is empty, false otherwise.
> + *
> + * This can be a pretty expensive function call. If this function is required
> + * in a performance critical path, we may have to maintain a global count
> + * of the list entries in the global dlock_list_heads structure instead.
> + */
> +bool dlock_lists_empty(struct dlock_list_heads *dlist)
> +{
> +     int idx;
> +
> +     for (idx = 0; idx < nr_cpu_ids; idx++)
> +             if (!list_empty(&dlist->heads[idx].list))
> +                     return false;
> +     return true;
> +}

Umm...  How would one use it, anyway?  You'd need to stop all insertions
first, wouldn't you?

> + */
> +struct dlock_list_node *__dlock_list_next_list(struct dlock_list_iter *iter)
> +{
> +     struct dlock_list_node *next;
> +     struct dlock_list_head *head;
> +
> +restart:
> +     if (iter->entry) {
> +             spin_unlock(&iter->entry->lock);
> +             iter->entry = NULL;
> +     }
> +
> +next_list:
> +     /*
> +      * Try next list
> +      */
> +     if (++iter->index >= nr_cpu_ids)
> +             return NULL;    /* All the entries iterated */
> +
> +     if (list_empty(&iter->head[iter->index].list))
> +             goto next_list;
> +
> +     head = iter->entry = &iter->head[iter->index];
> +     spin_lock(&head->lock);
> +     /*
> +      * There is a slight chance that the list may become empty just
> +      * before the lock is acquired. So an additional check is
> +      * needed to make sure that a valid node will be returned.
> +      */
> +     if (list_empty(&head->list))
> +             goto restart;
> +
> +     next = list_entry(head->list.next, struct dlock_list_node,
> +                       list);
> +     WARN_ON_ONCE(next->head != head);
> +
> +     return next;
> +}

Perhaps something like

        if (iter->entry) {
                spin_unlock(&iter->entry->lock);
                iter->entry = NULL;
        }
        while (++iter->index < nr_cpu_ids) {
                struct dlock_list_head *head = &iter->head[iter->index];

                if (list_empty(head->list))
                        continue;

                spin_lock(&head->lock);
                // recheck under lock
                if (unlikely(list_empty(&head->list))) {
                        spin_unlock(&head->lock);
                        continue;
                }

                iter->entry = head;
                next = list_first_entry(&head->list,
                                        struct dlock_list_node, list);
                WARN_ON_ONCE(next->head != head);
                return next;
        }
        return NULL;

Reply via email to