Date: Sun, 30 Nov 2003 09:18:22 +0800 From: David Xu <davidxu@viatech.com.cn> To: "Christopher M. Sedore" <cmsedore@maxwell.syr.edu> Cc: threads@freebsd.org Subject: Re: KSE system scope vs non system scope threads Message-ID: <3FC9455E.6030802@viatech.com.cn> In-Reply-To: <32A8B2CB12BFC84D8D11D872C787AA9A515DAE@EXCHANGE.forest.maxwell.syr.edu> References: <32A8B2CB12BFC84D8D11D872C787AA9A515DAE@EXCHANGE.forest.maxwell.syr.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Can you checkout src/lib/libpthread/thread/thr_spinlock.c revision 1.18 and see any differents ? David Xu Christopher M. Sedore wrote: > >I have a fairly simple question about KSE threads: In a threaded program using KSE threads, what is the effective difference between a system-scope thread and a non-system-scope thread? If I understand the KSE architecture correctly, there should not be a significant functional difference. If my reading lead me to the right conclusion, at the nitty-gritty level, there are multiple KSE groups created with system-scope threads, as I understand it, meaning that the kernel scheduler actually does the scheduling work for system-scope threads, instead of the userland KSE scheduler. > >I ask this because I'm observing some behavior that I don't expect. When running a threaded program with KSE and non-system-scope threads, I see performance degradation in my network traffic when I'm attempting to connect to remote hosts that are down. Libthr doesn't see this degradation, and KSE with system-scope threads doesn't perform as well as libthr, but is much closer. > >If there is a canonical document that describes all this, a pointer would be very welcome. > >-Chris >_______________________________________________ >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" > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FC9455E.6030802>