[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTiltWgLtf2_pIu57-7V_Ya_PvOa5y75t_BwCvAtg@mail.gmail.com>
Date: Sat, 26 Jun 2010 09:26:05 +0800
From: huang ying <huang.ying.caritas@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Huang Ying <ying.huang@...el.com>, Ingo Molnar <mingo@...e.hu>,
"H.Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
Andi Kleen <andi@...stfloor.org>, tglx <tglx@...utronix.de>,
davem <davem@...emloft.net>, paulus <paulus@...ba.org>
Subject: Re: [RFC][PATCH] irq_work -v2
On Sat, Jun 26, 2010 at 2:30 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> +
> +static DEFINE_PER_CPU(struct irq_work *, irq_work_list);
> +
> +/*
> + * Claim the entry so that no one else will poke at it.
> + */
> +static bool irq_work_claim(struct irq_work *entry)
> +{
> + unsigned long flags;
> +
> + do {
> + flags = (unsigned long)entry->next;
> + if (flags & IRQ_WORK_PENDING)
> + return false;
> + } while (cmpxchg(&entry->next, flags, flags | IRQ_WORK_FLAGS) != flags);
> +
> + return true;
> +}
> +
> +
> +void __weak arch_irq_work_raise(void)
> +{
> + /*
> + * Lame architectures will get the timer tick callback
> + */
> +}
> +
> +/*
> + * Queue the entry and raise the IPI if needed.
> + */
> +static void __irq_work_queue(struct irq_work *entry)
> +{
> + struct irq_work **head;
> +
> + head = &get_cpu_var(irq_work_list);
> +
> + do {
> + /*
> + * Can assign non-atomic because we keep the flags set.
> + */
> + entry->next = next_flags(*head, IRQ_WORK_FLAGS);
> + } while (cmpxchg(head, entry->next, entry) != entry->next);
*head & IRQ_WORK_FLAGS == 0, but entry->next & IRQ_WORK_FLAGS ==
IRQ_WORK_FLAGS. So the cmpxchg will never succeed.
> +
> + /*
> + * The list was empty, raise self-interrupt to start processing.
> + */
> + if (!irq_work_next(entry))
> + arch_irq_work_raise();
> +
> + put_cpu_var(irq_work_list);
> +}
Best Regards,
Huang Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists