Date: Thu, 13 Nov 2008 18:37:47 -0800 (PST)
Message-Id: <20081113.183747.184760657.davem@davemloft.net>
To: travis@sgi.com
Cc: paulus@samba.org, akpm@linux-foundation.org, yinghai@kernel.org,
       mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparse_irq aka dyn_irq v13
From: David Miller <davem@davemloft.net>
In-Reply-To: <491CC8D7.7030306@sgi.com>
References: <491CC310.3050807@sgi.com>
	<20081113.162144.155677034.davem@davemloft.net>
	<491CC8D7.7030306@sgi.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 853
Lines: 19

From: Mike Travis <travis@sgi.com>
Date: Thu, 13 Nov 2008 16:39:51 -0800

> There's been a couple of different proposals to attempt to disassociate
> i/o and system vectors though even attempting to guess at the number of
> i/o devices is tricky.  Every one of the 512 nodes on a UV system *may*
> have a number of i/o devices attached to them though practically this
> will be rare. 

Practicality is what really matters.

We can even make the constant number a config option, so that if
someone has a system that actually triggers past this limit even dist
vendors can simply bump the config option value.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/