From: Jon Smirl <jonsmirl@gmail.com>
To: Peter Chubb <peterc@gelato.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: User mode drivers: part 1, interrupt handling (patch for 2.6.11)
Date: Mon, 14 Mar 2005 22:19:37 -0500 [thread overview]
Message-ID: <9e47339105031419195bae4e11@mail.gmail.com> (raw)
In-Reply-To: <16948.60419.257853.470644@wombat.chubb.wattle.id.au>
On Mon, 14 Mar 2005 12:42:27 +1100, Peter Chubb
<peterc@gelato.unsw.edu.au> wrote:
> >>>>> "Jon" == Jon Smirl <jonsmirl@gmail.com> writes:
>
> >> The scenario I'm thinking about with these patches are things like
> >> low-latency user-level networking between nodes in a cluster, where
> >> for good performance even with a kernel driver you don't want to
> >> share your interrupt line with anything else.
>
> Jon> The code needs to refuse to install if the IRQ line is shared.
>
> It does. The request_irq() call explicitly does not include SA_SHARED
> in its flags, so if the line is shared, it'll return an error to user
> space when the driver tries to open the file representing the interrupt.
Please put some big comments warning people about adding SA_SHARED. I
can easily see someone thinking that they are fixing a bug by adding
it. I'd probably even write a paragraph about what will happen if
SA_SHARED is added.
>
> Jon> Also what about SMP, if you shut the IRQ off on one CPU isn't it
> Jon> still enabled on all of the others?
>
> Nope. disable_irq_nosync() talks to the interrupt controller, which
> is common to all the processors. The main problem is that it's slow,
> because it has to go off-chip.
>
> --
> Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
> The technical we do immediately, the political takes *forever*
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-03-15 3:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 3:36 User mode drivers: part 1, interrupt handling (patch for 2.6.11) Peter Chubb
2005-03-11 10:29 ` Pavel Machek
2005-03-12 16:27 ` Jon Smirl
2005-03-12 18:55 ` Jon Smirl
2005-03-14 0:39 ` Peter Chubb
2005-03-14 1:24 ` Jon Smirl
2005-03-11 13:50 ` Michael Raymond
2005-03-11 17:25 ` Greg KH
2005-03-11 17:31 ` Michael Raymond
2005-03-11 19:14 ` Alan Cox
2005-03-13 2:03 ` Jon Smirl
2005-03-15 4:32 ` Lee Revell
2005-03-15 13:28 ` Alan Cox
2005-03-14 0:02 ` Peter Chubb
2005-03-14 13:33 ` Alan Cox
2005-03-15 3:15 ` Jon Smirl
2005-03-12 15:55 ` Jon Smirl
2005-03-12 17:11 ` Zwane Mwaikambo
2005-03-14 1:55 ` Jon Smirl
2005-03-14 3:04 ` Peter Chubb
2005-03-14 0:36 ` Peter Chubb
[not found] ` <9e47339105031317193c28cbcf@mail.gmail.com>
2005-03-14 1:42 ` Peter Chubb
2005-03-14 1:52 ` Jon Smirl
2005-03-14 3:06 ` Peter Chubb
2005-03-15 3:19 ` Jon Smirl [this message]
2005-03-15 3:47 ` Peter Chubb
2005-03-15 3:50 ` Jon Smirl
2005-03-15 4:11 ` Peter Chubb
-- strict thread matches above, loose matches on Subject: below --
2005-03-15 19:20 Stephen Warren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e47339105031419195bae4e11@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterc@gelato.unsw.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.