[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <adaskf6od3h.fsf@cisco.com>
Date: Tue, 01 Sep 2009 09:15:46 -0700
From: Roland Dreier <rdreier@...co.com>
To: Christoph Lameter <cl@...ux-foundation.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Gregory Haskins <ghaskins@...ell.com>,
Rik van Riel <riel@...hat.com>,
Chris Friesen <cfriesen@...tel.com>,
raz ben yehuda <raziebe@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu,
peterz@...radead.org, maximlevitsky@...il.com, efault@....de,
wiseman@...s.biu.ac.il, linux-kernel@...r.kernel.org,
linux-rt-users@...r.kernel.org
Subject: Re: RFC: THE OFFLINE SCHEDULER
> Ok then these per cpu irqs are there to support something different? There
> are per cpu irqs here. Seems to be hardware supported?
Yes, the driver now creates per-cpu IRQs for completions. However if
you don't trigger any completion events then you won't get any
interrupts. That's different from the workqueues, which are used to
poll the hardware for port changes and internal errors (and which are
single-threaded and can be put on whatever "system services" CPU you want)
- R.
--
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