Date: Wed, 21 Jun 2000 08:39:02 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Nick Hibma <n_hibma@calcaphon.com> Cc: freebsd-smp@freebsd.org Subject: Re: irunning, width in bits. Message-ID: <200006211539.IAA94918@apollo.backplane.com> References: <Pine.BSF.4.20.0006210034060.34122-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
(Moving this to freebsd-smp, Bcc'ing current)
:What about shared interrupts? How are they going to be treated? With the
:spl leaving the arena it somehow looks feasible to run one interrupt
:source on two different threads if there are two pieces of hardware
:attached to the same interrupt line.
:
:>From what I understood from dfr, when switching away from an interrupt
:handler it is converted into a full thread. When the second piece of
:hardware fires an interrupt it could then run at the same time.
:
:Nick
:--
:n_hibma@webweaving.org
This came up at the meeting and the conclusion was that shared
interrupts would run serially. That is, each 'bit' in the cpl
(spl*(), also represented by ipending, the vector table dispatch, and
so forth) would be treated as a single interrupt thread. If there
are N interrupts hanging off that IRQ, then each of the N would
be run serially from a single interrupt thread.
This also came up a few months ago, you can probably find the discussion
in the archives.
What it comes down to is complexity and convenience. In almost all
systems it is possible to rearrange the PCI boards such that you do
not have two critical interrupts on the same IRQ.
We are not precluding being able to schedule shared interrupts separately,
but if we are going to do it it will probably be much later when things
are more stable and not now. The KISS principle applies here.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006211539.IAA94918>