public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: [RFC][patch 0/10] Multiple vector domain support
Date: Thu, 14 Jul 2005 09:15:07 +0000	[thread overview]
Message-ID: <42D62D1B.8000105@jp.fujitsu.com> (raw)

Hi,

I'm attaching the series of patches for handling huge number of
interrtupt sources. This patch is to increase vector spaces by
separating processors into some domains. This idea is the same as "per
node IDT" posted by Zwane Mwaikambo at:

    http://marc.theaimsgroup.com/?l=linux-kernel&m\x112103551401596&w=2

The ia64 linux already have vector sharing to handle huge number of
level-triggered interrupt sources via I/O SAPIC, but I think we also
need per domain vector approach because:

    o Supporting vector shairng for edge-triggered interrupts is
      difficult (or impossible)

    o Vector domain approach has better performance than vector
      sharing

    o Need to support MSI based interrupts

This series of patches is still under development, and has following
TBD items.

    o How to create vector domains

      Need to consider how to create vector domains(per CPU?, per
      node? or others...)

    o MSI support

      Attached patch only supports vector domain for I/O SAPIC
      interrupts. We need to consider how to support vector domain for
      MSI interrupts.

    o /proc interface

    o How to handle CPU hotplug

    o and so on..


Any comments and questions are welcomed.

Thanks,
Kenji Kaneshige



                 reply	other threads:[~2005-07-14  9:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=42D62D1B.8000105@jp.fujitsu.com \
    --to=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-ia64@vger.kernel.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