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 ...

[David Xu]

Sorry, I am too pugnacious. :-)

David Xu

----- Original Message ----- 
From: "Scott Long" <scottl at freebsd.org>
To: "David Xu" <davidxu at viatech.com.cn>
Cc: <src-committers at freebsd.org>; <cvs-src at freebsd.org>; <cvs-all at freebsd.org>
Sent: Tuesday, June 17, 2003 12:47 PM
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 ...


> I apologize for coming on stronger than I meant.  It likely comes
> down to personal style, so there is no use in wasting effort arguing
> about it.
> 
> Scott
> 
> David Xu wrote:
> > 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. 
> > 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