From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Andrew Morton <akpm@osdl.org>, Len Brown <len.brown@intel.com>,
"Luck, Tony" <tony.luck@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: [PATCH] IRQ resource deallocation[0/2]
Date: Tue, 07 Dec 2004 16:21:01 +0900 [thread overview]
Message-ID: <41B559DD.7040307@jp.fujitsu.com> (raw)
Hi,
I had posted the IRQ resource deallocation patch a couple of monthes
ago and I had incorporated all feedbacks from the mailing list
(http://marc.theaimsgroup.com/?l=linux-kernel&m=109688530703122&w=2).
But it doesn't seems to be included yet, so I would like to try again.
I hope my patch is included onto -mm tree since I want the patches
be tested by many people.
Here is a brief description:
Architecture dependent IRQ resources such as interrupt vector for PCI
devices are allocated at pci_enable_device() time on i386, x86-64 and
ia64 platform. Today, however, these IRQ resources are never
deallocated even if they are no longer used. The following set of
patches adds supports to deallocate IRQ resources at
pci_disable_device() time.
The motivation of the set of patches is as follows:
- IRQ resources such as interrupt vectors should be freed if they
are no longer used because the amount of these resources are
limited. By deallocating IRQ resources, we can recycle them.
- I think some hardwares will support hot-pluggable I/O units with
I/O xAPICs in the near future. So I/O xAPIC hot-plug support by
OS will be needed soon. IRQ resouces deallocation will be one of
the most important stuff for I/O xAPIC hot-plug.
For now, the following set of patches has ia64 implementation only.
i386 and x86_64 implementations are TBD.
The patches are against 2.6.10-rc3.
Thanks,
Kenji Kaneshige
next reply other threads:[~2004-12-07 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 7:21 Kenji Kaneshige [this message]
2004-12-07 15:22 ` [PATCH] IRQ resource deallocation[0/2] Zwane Mwaikambo
2004-12-08 7:07 ` Kenji Kaneshige
2004-12-10 6:13 ` Kenji Kaneshige
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=41B559DD.7040307@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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