Date: Fri, 18 Jun 2004 16:56:56 +0800 From: David Xu <davidxu@freebsd.org> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-threads@freebsd.org Subject: Re: Possible Threading problem with -CURRENT / MySQL? Message-ID: <40D2AE58.3040303@freebsd.org> In-Reply-To: <Pine.NEB.3.96L.1040617085226.13466F-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1040617085226.13466F-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
When this pthread program runs under ULE, I can not interrupt it pressing ctrl+c has no effect, I have this problem for a long time. http://people.freebsd.org/~davidxu/kse/locktest.c David Xu Robert Watson wrote: > ULE seems to do a very good job of scheduling interactive tasks over > other > workloads, resulting in a very "snappy" feel on my boxes, despite heavy > CPU load from background builds, etc. The workload I looked at had no > real "interactive" component, although it was a latency-centric RPC > test, > so timely hand-off as well as high throughput would be important. I > know > that Jeff's measurement work on ULE had a substantial focus on deadlines > -- whether or not ULE was timely in scheduling tasks, etc, and that he > demonstrated that it was much stronger than most other available > schedulers in this area. > > One of the next obvious steps in optimizing either ULE or 4BSD is going > to > be to spend a lot of time sitting with KTR(4) and looking at context > switch traces for "dumb things", such as bouncing between CPUs, rapid > switches back and forth, undo multiple wakeups, etc. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Senior Research Scientist, McAfee Research > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40D2AE58.3040303>