From owner-freebsd-arch Tue May 7 12:31:18 2002 Delivered-To: freebsd-arch@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 762A137B40A; Tue, 7 May 2002 12:31:13 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g47JVDh84057; Tue, 7 May 2002 12:31:13 -0700 (PDT) (envelope-from dillon) Date: Tue, 7 May 2002 12:31:13 -0700 (PDT) From: Matthew Dillon Message-Id: <200205071931.g47JVDh84057@apollo.backplane.com> To: Robert Watson Cc: John Baldwin , arch@FreeBSD.org, Poul-Henning Kamp Subject: Re: syscall changes to deal with 32->64 changes. References: Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :> I'm also not sure if we shouldn't wait to do this until 6.0. : :Well, that's the big question, really. If we can do it in the time frame, :why wait, as they say :-). If we can't, then it's a 6.0 thing. 5.0 is a :nice breaking point -- we're ripping up so much anyway, and we'd like to :get the ABI changes for UFS2 in. But if the schedule isn't realistic, :then we can't -- slipping 5.0-release any further isn't something I want :to let happen. : :Robert N M Watson FreeBSD Core Team, TrustedBSD Project I think the one big advantage with having a new syscall vector is precisely the fact that the new ABI can be worked on without effecting the existing system. Internal system support that is still 32 bits winds up being straight-up in the old syscall vector and extended out in the new, and internal system support that has been changed to 64 bits winds up being truncated in the old syscall vector and straight up in the new. Either way we are able to maintain ABI compatibility for both syscall vectors even if it takes months to convert all the kernel subsystems to the new sizes. This seems to infer that the work will not directly interfere with 5.0R, even if it is not 100% complete by the release. That would make the work 'a go' in my book. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message