Date: Tue, 17 Jun 2003 08:11:34 +0800 From: "David Xu" <davidxu@freebsd.org> To: "Scott Long" <scottl@freebsd.org> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/alpha/linux linux_sysvec.c src/sys/amd64/amd64 pmap.c trap.c src/sys/compat/svr4 svr4_sysvec.c src/sys/ddb db_ps.c src/sys/fs/procfs procfs_status.c src/sys/i386/i386 pmap.c ... Message-ID: <001501c33465$04b11040$0701a8c0@tiger> References: <200306150031.h5F0VPse055534@repoman.freebsd.org> <3EEE0F0C.3030205@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
What does KSE mean ? I think kse is only useful for scheduler, I would like it disappears in kse_thread.c and only becomes a scheduler private data structure, current kern_thread.c is forced to manage kse data structure but no code is really using it in that file. Julian even ever said ksegrp should be a subproc, I think he is right.=20 If someone want to implement another SA, feel free to do, but there is no reason that our SA implement should be called P_KSE and a future not implemented yet should be called P_SA or P_SAxxx. :( David Xu ----- Original Message -----=20 From: "Scott Long" <scottl@freebsd.org> To: "David Xu" <davidxu@freebsd.org> Cc: <src-committers@freebsd.org>; <cvs-src@freebsd.org>; = <cvs-all@freebsd.org> Sent: Tuesday, June 17, 2003 2:40 AM Subject: Re: cvs commit: src/sys/alpha/alpha trap.c src/sys/alpha/linux = linux_sysvec.c src/sys/amd64/amd64 pmap.c trap.c src/sys/compat/svr4 = svr4_sysvec.c src/sys/ddb db_ps.c src/sys/fs/procfs procfs_status.c = src/sys/i386/i386 pmap.c ... > It would have been more appropriate to revert the name to P_KSE rather > than give it yet another name. What happens when someone comes along > and wants to experiment with another SA-like implementation? >=20 > Scott >=20 > David Xu wrote: > > davidxu 2003/06/14 17:31:25 PDT > >=20 > > FreeBSD src repository > >=20 > > Modified files: > > sys/alpha/alpha trap.c=20 > > sys/alpha/linux linux_sysvec.c=20 > > sys/amd64/amd64 pmap.c trap.c=20 > > sys/compat/svr4 svr4_sysvec.c=20 > > sys/ddb db_ps.c=20 > > sys/fs/procfs procfs_status.c=20 > > sys/i386/i386 pmap.c sys_machdep.c trap.c=20 > > sys/i386/linux linux_sysvec.c=20 > > sys/ia64/ia64 trap.c=20 > > sys/kern kern_clock.c kern_exec.c kern_exit.c=20 > > kern_fork.c kern_sig.c kern_switch.c=20 > > kern_synch.c kern_thread.c sched_4bsd.c=20 > > sched_ule.c subr_trap.c tty.c=20 > > sys/sparc64/sparc64 trap.c=20 > > sys/sys proc.h=20 > > Log: > > Rename P_THREADED to P_SA. P_SA means a process is using scheduler > > activations. > > =20 > > Revision Changes Path > > 1.115 +1 -1 src/sys/alpha/alpha/trap.c > > 1.89 +1 -1 src/sys/alpha/linux/linux_sysvec.c > > 1.411 +1 -1 src/sys/amd64/amd64/pmap.c > > 1.261 +1 -1 src/sys/amd64/amd64/trap.c > > 1.33 +1 -1 src/sys/compat/svr4/svr4_sysvec.c > > 1.46 +3 -3 src/sys/ddb/db_ps.c > > 1.49 +1 -1 src/sys/fs/procfs/procfs_status.c > > 1.411 +1 -1 src/sys/i386/i386/pmap.c > > 1.83 +1 -1 src/sys/i386/i386/sys_machdep.c > > 1.254 +1 -1 src/sys/i386/i386/trap.c > > 1.125 +1 -1 src/sys/i386/linux/linux_sysvec.c > > 1.83 +1 -1 src/sys/ia64/ia64/trap.c > > 1.160 +3 -3 src/sys/kern/kern_clock.c > > 1.224 +2 -2 src/sys/kern/kern_exec.c > > 1.217 +2 -2 src/sys/kern/kern_exit.c > > 1.202 +3 -3 src/sys/kern/kern_fork.c > > 1.242 +1 -1 src/sys/kern/kern_sig.c > > 1.60 +5 -5 src/sys/kern/kern_switch.c > > 1.226 +2 -2 src/sys/kern/kern_synch.c > > 1.140 +6 -6 src/sys/kern/kern_thread.c > > 1.20 +1 -1 src/sys/kern/sched_4bsd.c > > 1.38 +1 -1 src/sys/kern/sched_ule.c > > 1.256 +2 -2 src/sys/kern/subr_trap.c > > 1.203 +1 -1 src/sys/kern/tty.c > > 1.63 +1 -1 src/sys/sparc64/sparc64/trap.c > > 1.337 +1 -1 src/sys/sys/proc.h > >=20 >=20 >=20 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001501c33465$04b11040$0701a8c0>