From: "David S. Miller" <davem@redhat.com>
To: willy@debian.org
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org,
ink@jurassic.park.msu.ru
Subject: Re: Message Signalled Interrupt support?
Date: Mon, 12 May 2003 10:20:23 -0700 (PDT) [thread overview]
Message-ID: <20030512.102023.71099561.davem@redhat.com> (raw)
In-Reply-To: <20030512165331.GZ29534@parcelfarce.linux.theplanet.co.uk>
From: Matthew Wilcox <willy@debian.org>
Date: Mon, 12 May 2003 17:53:31 +0100
On Mon, May 12, 2003 at 12:32:49PM -0400, Jeff Garzik wrote:
> Has anybody done any work, or put any thought, into MSI support?
Work -- no. Thought? A little. Seems to me that MSIs need to be
treated as a third form of interrupts (level/edge/message).
The fact that Alpha already supports them pretty much transparently
suggests that the thing to do might very well be "nothing" :-)
To be honest, MSIs are very similar to how interrupts work on sparc64,
in that each device generates a unique interrupt cookie. The only
different is the size of this cookie, MSIs are larger than sparc64's.
next prev parent reply other threads:[~2003-05-12 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 16:32 Message Signalled Interrupt support? Jeff Garzik
2003-05-12 16:53 ` Matthew Wilcox
2003-05-12 17:20 ` David S. Miller [this message]
2003-05-12 18:54 ` Mika Penttilä
2003-05-12 17:43 ` Matt Porter
2003-05-12 18:20 ` Matthew Wilcox
2003-05-12 18:48 ` Matt Porter
2003-05-13 11:21 ` Ivan Kokshaysky
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 17:26 Chuck Ebbert
2003-05-12 17:53 Nakajima, Jun
2003-05-12 18:26 Nakajima, Jun
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=20030512.102023.71099561.davem@redhat.com \
--to=davem@redhat.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox