From owner-freebsd-threads@FreeBSD.ORG Wed Apr 16 09:30:19 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A732037B401 for ; Wed, 16 Apr 2003 09:30:19 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC39E43FBD for ; Wed, 16 Apr 2003 09:30:18 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by rwcrmhc51.attbi.com (rwcrmhc51) with ESMTP id <2003041616301805100hsoa8e>; Wed, 16 Apr 2003 16:30:18 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id JAA43553; Wed, 16 Apr 2003 09:30:15 -0700 (PDT) Date: Wed, 16 Apr 2003 09:30:08 -0700 (PDT) From: Julian Elischer To: Jeff Roberson In-Reply-To: <20030416020803.D76635-100000@mail.chesapeake.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org Subject: Re: struct kse X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2003 16:30:20 -0000 On Wed, 16 Apr 2003, Jeff Roberson wrote: > > Can we totally nuke ke_oncpu since it's only used in one place? > > Also, KEF_DIDRUN is sched_4bsd specific. I may move this. yes. ke_oncpu was only a placeholder for me to replace it with ke_pincpu(jhb's name), the CPU that KSE is nailed (pinned) to if we implement affinity/nailing. However that'll probably require special variables so it should go away. > > If we move the KEF_IDLEKSE as a property of the idle thread instead and do > something else with KEF_EXIT we could remove ke_flags. yes, I was going to suggest that the idle flag could go to the thread.. it removes knowledge of the KSE from at least one file.. > > ke_pctcpu is also scheduler specific although it is referenced from > kinfo_proc so I wont move it yet. It's scheduler specific but the outside world is also scheduler specific in its expectations :-/ > > Comments? > Jeff > > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >