From owner-p4-projects@FreeBSD.ORG Fri Jan 9 13:22:58 2004 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 89B5616A4D1; Fri, 9 Jan 2004 13:22:58 -0800 (PST) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6408716A4CE for ; Fri, 9 Jan 2004 13:22:58 -0800 (PST) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5997843D3F for ; Fri, 9 Jan 2004 13:22:57 -0800 (PST) (envelope-from jhb@freebsd.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.12.10/8.12.10) with ESMTP id i09LMv0B078499 for ; Fri, 9 Jan 2004 13:22:57 -0800 (PST) (envelope-from jhb@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.12.10/8.12.10/Submit) id i09LMu4W078496 for perforce@freebsd.org; Fri, 9 Jan 2004 13:22:56 -0800 (PST) (envelope-from jhb@freebsd.org) Date: Fri, 9 Jan 2004 13:22:56 -0800 (PST) Message-Id: <200401092122.i09LMu4W078496@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to jhb@freebsd.org using -f From: John Baldwin To: Perforce Change Reviews Subject: PERFORCE change 45033 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2004 21:22:59 -0000 http://perforce.freebsd.org/chv.cgi?CH=45033 Change 45033 by jhb@jhb_slimer on 2004/01/09 13:22:53 Add notes about kthread/kproc cleanup. Affected files ... .. //depot/projects/smpng/sys/notes#4 edit Differences ... ==== //depot/projects/smpng/sys/notes#4 (text+ko) ==== @@ -50,5 +50,13 @@ - Minor fixes to taskqueue locking including making the locking for the taskqueue thread queeu actually work. - Untested +- Add a kproc API that does what kthread does right now +- Add a real kthread API that creates just another thread inside of a kproc + - Figure out what needs to be done to make a new kthread.. should each + kproc have one ksegroup and one kse per cpu? + - Do I just add the kse's when the first new thread is created? + - Consolidate most of the kernel procs into a 'system' kernel proc that + would be pid 0. + - Stick all the 'idle threads' in a single 'idle' kernel proc. Space reserved for child branches: