Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262192AbTEUQSd (ORCPT ); Wed, 21 May 2003 12:18:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262193AbTEUQSd (ORCPT ); Wed, 21 May 2003 12:18:33 -0400 Received: from nat9.steeleye.com ([65.114.3.137]:8452 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id S262192AbTEUQSc (ORCPT ); Wed, 21 May 2003 12:18:32 -0400 Subject: Re: userspace irq balancer From: James Bottomley To: Linux Kernel Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-9) Date: 21 May 2003 11:31:30 -0500 Message-Id: <1053534694.1681.10.camel@mulgrave> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 845 Lines: 25 I'm interested in using this for voyager. However, I have a problem in that voyager may have CPUs that can't accept interrupts (this is global on voyager, but may be per-interrupt on NUMA like systems). I think before we move to a userspace solution, some thought about how to cope with this is needed. I have several suggestions: 1. Place the masks into /proc/irq//smp_affinity at start of day and have the userspace irqbalancer take this as the maximal mask 2. Have a separate file /proc/irq//mask(?) to expose the mask always 3. Some other method... Comments would be welcome James - 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/