From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH][RFC] Vector sharing
Date: Thu, 22 Apr 2004 02:37:58 +0000 [thread overview]
Message-ID: <MDEEKOKJPMPMKGHIFAMAOEELDNAA.kaneshige.kenji@jp.fujitsu.com> (raw)
In-Reply-To: <MDEEKOKJPMPMKGHIFAMAOENCDMAA.kaneshige.kenji@jp.fujitsu.com>
Hi Jean-Francois,
> I agree with you ACPI IRQ cleanup patch or my patch only stops the
> waste of the vector resource for line not used but doesn't solve the
> problem completely.
Thank you :)
> In addition with on of theses patch our patch set_rte() should get
> iosapic_lock is mandatory.
I think both of your patch needs to get iosapic_lock in
iosapic_register_intr()
also. Please see following message:
http://www.gelato.unsw.edu.au/linux-ia64/0404/9352.html
Thanks,
Kenji Kaneshige
-----Original Message-----
From: Jean-Francois Neyroud [mailto:Jean-Francois.Neyroud@bull.net]
Sent: Wednesday, April 21, 2004 3:26 PM
To: Kenji Kaneshige
Cc: linux-ia64@vger.kernel.org; Bjorn Helgaas
Subject: Re: [PATCH][RFC] Vector sharing
Kenji Kaneshige wrote:
Hi,
Thank you for your comments.
An other or complementary way is to attach a vector only for interrupt
lines witch are used, PCI slots have 4 interrupt lines but only 1 or
sometime 2 are used by adapters.
I agree with attaching a vector only for interrupt lines which are used.
Your patch stops the waste of the vector resource, and it becomes difficult
for the lack of vectors to happen. I think we can also do this by using
Bjorn's
ACPI IRQ cleanup patch. To tell the truth, I also had a same idea before.
However, this idea doesn't solve the problem completely. The problem will
happen in the following case:
o many PCI adapters have 2 or more functions
o machine has more than 184 PCI slots in the same domain
So, I think vector sharing is necessary to solve this problem.
I agree with you ACPI IRQ cleanup patch or my patch only stops the waste of
the vector resource for line not used but doesn't solve the problem
completely.
In addition with on of theses patch our patch set_rte() should get
iosapic_lock is mandatory.
Jean-Francois
next prev parent reply other threads:[~2004-04-22 2:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 9:31 [PATCH][RFC] Vector sharing Kenji Kaneshige
2004-04-20 12:25 ` Jean-Francois Neyroud
2004-04-20 14:46 ` Bjorn Helgaas
2004-04-21 1:15 ` Kenji Kaneshige
2004-04-21 1:37 ` Kenji Kaneshige
2004-04-22 2:37 ` Kenji Kaneshige [this message]
2004-04-23 7:09 ` 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=MDEEKOKJPMPMKGHIFAMAOEELDNAA.kaneshige.kenji@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