From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932562Ab1EYMsf (ORCPT ); Wed, 25 May 2011 08:48:35 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:50932 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932207Ab1EYMsb (ORCPT ); Wed, 25 May 2011 08:48:31 -0400 Date: Wed, 25 May 2011 14:47:41 +0200 From: Ingo Molnar To: Geert Uytterhoeven Cc: Valdis.Kletnieks@vt.edu, "Eric W. Biederman" , James Bottomley , Linus Torvalds , linux-kernel@vger.kernel.org, Linux Containers , netdev@vger.kernel.org Subject: Re: [GIT PULL] Namespace file descriptors for 2.6.40 Message-ID: <20110525124741.GC29300@elte.hu> References: <1306048393.4092.8.camel@mulgrave.site> <20110522084224.GA12279@elte.hu> <20110524071628.GA31612@elte.hu> <4508.1306283693@localhost> <20110525082514.GE21552@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Geert Uytterhoeven wrote: > > But at least the primary, 'native' syscall table of every arch > > could be kept rather fresh via generic enumeration. > > So we can start all over at offset 501 (alpha just started using > 500) with a unified, clean, and compressed list of syscalls? Or do > we have some more other-os-compat syscalls around in this range? No, that would leave a big hole in the syscall table of most architectures. So what would be needed is for each architecture to define a 'generic syscall table base index', ARCH_SYSCALL_BASE or so, and the generic syscalls would be added for that. Alpha would have 501, the others lower numbers. The only general assumption we can rely on is that there's a range of not yet used syscall numbers starting at the end of the current syscall table. Thanks, Ingo