From owner-cvs-src@FreeBSD.ORG Fri Jul 18 18:21:46 2003 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F3B37B401; Fri, 18 Jul 2003 18:21:46 -0700 (PDT) Received: from magic.adaptec.com (magic-mail.adaptec.com [208.236.45.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9C8F43F85; Fri, 18 Jul 2003 18:21:45 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6/8.11.6) with ESMTP id h6J1Ljs31549; Fri, 18 Jul 2003 18:21:45 -0700 Received: from freebsd.org ([10.100.253.187]) by redfish.adaptec.com (8.8.8p2+Sun/8.8.8) with ESMTP id SAA02931; Fri, 18 Jul 2003 18:21:44 -0700 (PDT) Message-ID: <3F189D20.2050709@freebsd.org> Date: Fri, 18 Jul 2003 19:21:36 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: deischen@freebsd.org cc: David O'Brien cc: src-committers@freebsd.org cc: David Xu cc: cvs-src@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/lib/libpthread Makefile src/lib/libpthread/test thr_create.cthr_private.h thr_sig.c thr_sigmask.c ... X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2003 01:21:47 -0000 Julian Elischer wrote: > > On Fri, 18 Jul 2003, David O'Brien wrote: > > >>Who are "the arches"? KSE is a new feature, so the responsibility is on >>the KSE developers to complete their implementation on all Tier-1 >>platforms. I've offered Alpha boxes to all the KSE developers and have >>had zero takers... (same for i386 SMP boxes... but that's another story) >> > > > I dont know the alpha and having a box isn't going to help that. > I can "guide" soemone who DOES know it as to what the kernel > MD parts should do but I'm not in a position to code them. > > They are pretty trivial to describe, but you need to know a lot about > the architecture in question to know how each function should be > achieved. > > I guess what I should do is produce a recipe as to what needs to be > added to to each architecture's MD files to 'complete' that > architecture. With that I think specialists in each architecture should > have little problem filling in the gaps. > That would be an excellent start =-) Scott