| From | Sent On | Attachments |
|---|---|---|
| Daniel Eischen | Oct 13, 2000 3:32 pm | |
| jd...@polstra.com | Oct 14, 2000 3:08 am | |
| Daniel Eischen | Oct 14, 2000 6:33 am | |
| jd...@polstra.com | Oct 14, 2000 1:00 pm | |
| Daniel Eischen | Oct 14, 2000 9:19 pm | |
| Gerhard Sittig | Oct 15, 2000 3:38 am | |
| jd...@polstra.com | Oct 16, 2000 7:00 pm | |
| Daniel M. Eischen | Oct 16, 2000 7:33 pm |
| Subject: | Re: Recent thread changes | |
|---|---|---|
| From: | jd...@polstra.com (jd...@polstra.com) | |
| Date: | Oct 14, 2000 3:08:32 am | |
| List: | org.freebsd.freebsd-current | |
In article <2000...@pcnet1.pcnet.com>, Daniel Eischen <eisc...@vigrid.com> wrote:
I've just committed some changes to the threads library and would appreciate feedback from anyone running threaded applications. They include fixes that -stable could really use.
This commit also implements zero system call thread context switching in the threads library. Switching between threads is now much faster than before this change.
This sounds like great stuff!
The range of valid priorities has also changed, perhaps requiring a library version bump. The range of valid priorities is not visible outside of the threads library. The only way it can be determined is through trial and error, so it _shouldn't_ be an issue.
I thought you could get that information with sched_get_priority_min() and sched_get_priority_max(). Is that not the case?
John
-- John Polstra jd...@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message





