From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org ([203.10.76.45]:28822 "EHLO ozlabs.org") by vger.kernel.org with ESMTP id S268805AbUIHA26 (ORCPT ); Tue, 7 Sep 2004 20:28:58 -0400 Date: Wed, 8 Sep 2004 10:24:08 +1000 From: Anton Blanchard Subject: Re: [PATCH] Fix argument checking in sched_setaffinity Message-ID: <20040908002408.GA25278@krispykreme> References: <20040904180548.2dcdd488.pj@sgi.com> <20040904204850.48b7cfbd.pj@sgi.com> <20040904211749.3f713a8a.pj@sgi.com> <20040904215205.0a067ab8.pj@sgi.com> <20040906182330.GA79122@muc.de> <20040906141142.663941fb.pj@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: To: Linus Torvalds Cc: Paul Jackson , ak@muc.de, Andrew Morton , Linux Arch list List-ID: > Now, it will _only_ break systems that are _both_ 64-bit _and_ big-endian. > Little-endian or 32-bit boxes will never care. > > There aren't that many of those machines. I've got one right here (ppc64), > but that particular one is guaranteed not to break if only because it's > running a 32-bit user space. > > So it's ppc64, sparc64, s390x and sh64. I suspect the breakage is > basically zero, since not only aren't there _that_ many machines out > there, the percentage of them that use setaffinity or mbind is likely not > that high either. Oh we've felt it all right, both the cpu affinity calls and the numa api calls that pass node bitmaps around. I'll resend what patches I currently have for this. Anton