From: | Mattias Kregert <matti(at)algonet(dot)se> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
Cc: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, Massimo Dal Zotto <dz(at)cs(dot)unitn(dot)it>, scrappy(at)hub(dot)org, hackers(at)postgreSQL(dot)org |
Subject: | Re: sched_yield() |
Date: | 1998-03-22 01:50:12 |
Message-ID: | 35146E54.A841F553@algonet.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The Hermit Hacker wrote:
>
> What's the possibility of doing this similar to how we do some of
> the other functions (dl_open comes immediately to mind)...make a
> pg_sched_yield function and use that, which is built based on the various
> platforms?
>
> Right now, I don't believe we have *anything* in place, so have
> pg_sched_yield() return 0 (or an equivalent) for every platform except for
> Linux...
But sched_yield() is not Linux-specific:
-- The sched_yield() function relinquishes the processor for the
-- running process.
-- IEEE Std 1003.1b-1993, §13.3.5. (POSIX real-time standard 1003.lb)
Except from Linux, I can find references to sched_yield() in LynxOS,
DECthreads thread library, AIX 4.1 and up (libc), Solaris (thread.h
(c)1994 Sun
Microsystems), Unix98, GNU, C EXECUTIVE(r) and PSX(tm) real time kernels
...
This is just a quick search.
Perhaps we should enable sched_yield() for every OS except for... well,
what's the
name of that OS which does not have sched_yield()... FreeBSD ;)
After all, sched_yield() is five years old. Any reasonable OS should
have it.
/* m */
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 1998-03-22 02:39:36 | Re: [HACKERS] Newest Patch...try this one... |
Previous Message | The Hermit Hacker | 1998-03-22 01:33:16 | Re: sched_yield() |