From owner-cvs-src@FreeBSD.ORG Thu Apr 10 12:23:41 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 60B9237B401; Thu, 10 Apr 2003 12:23:41 -0700 (PDT) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDBD443F85; Thu, 10 Apr 2003 12:23:39 -0700 (PDT) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h3AJNd858794; Thu, 10 Apr 2003 15:23:39 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Thu, 10 Apr 2003 15:23:39 -0400 (EDT) From: Jeff Roberson To: John Baldwin In-Reply-To: <20030410151504.R37530-100000@mail.chesapeake.net> Message-ID: <20030410152200.M37530-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: Julian Elischer cc: cvs-all@FreeBSD.org Subject: RE: cvs commit: src/sys/ddb db_ps.c src/sys/i386/i386 genassym.c kern_thread.c sched_4bsd.c sched_ule.c subr_smp.c subr_witness.c src/sys/ 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: Thu, 10 Apr 2003 19:23:41 -0000 On Thu, 10 Apr 2003, Jeff Roberson wrote: > > On Thu, 10 Apr 2003, John Baldwin wrote: > > > > > On 10-Apr-2003 Julian Elischer wrote: > > > julian 2003/04/10 10:35:45 PDT > > > > > > FreeBSD src repository > > > > > > Modified files: > > > sys/ddb db_ps.c > > > sys/i386/i386 genassym.c > > > sys/kern init_main.c kern_fork.c kern_mutex.c > > > kern_proc.c kern_thread.c sched_4bsd.c > > > sched_ule.c subr_smp.c subr_witness.c > > > sys/sys proc.h > > > Log: > > > Move the _oncpu entry from the KSE to the thread. > > > The entry in the KSE still exists but it's purpose will change a bit > > > when we add the ability to lock a KSE to a cpu. > > > > Why not add a ke_pincpu to hold the bound CPU? Since KSE's are in > > theory a kind of virtual CPU abstraction the thread really seems to > > be the wrong place for this information. > > > > Er, this seems wrong to me. Regardless, please but the bound cpu Sorry, moving the information to the thread seems wrong. I'm not sure I think it is such a good idea to so rigorously hide the kse structure. It may be nice to limit its scope but I think it is not so necessary and it leads to hacks like this where information is stored in a structure where it does not logically make sense. > information in the scheduler specific data. I already have an entry for > it in ULE. > > Cheers, > Jeff >