Re: [HACKERS] Re: sched_yield()
От
The Hermit Hacker
Тема
Re: [HACKERS] Re: sched_yield()
Дата
Msg-id
Pine.BSF.3.96.980322014347.324T-100000@thelab.hub.org
Ответ на
Re: [HACKERS] Re: sched_yield() (Bruce Momjian)
Список
Дерево обсуждения
Re: sched_yield() Mattias Kregert <matti@algonet.se>
Re: sched_yield() Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] Re: sched_yield() Tom <tom@sdf.com>
Re: sched_yield() The Hermit Hacker <scrappy@hub.org>
Re: sched_yield() Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] Re: sched_yield() dg@illustra.com (David Gould)
Re: [HACKERS] Re: sched_yield() Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] Re: sched_yield() The Hermit Hacker <scrappy@hub.org>
Re: [HACKERS] Re: sched_yield() The Hermit Hacker <scrappy@hub.org>
On Sat, 21 Mar 1998, Bruce Momjian wrote:
> > Secondly, the select() backoff patch I am working on starts out with a zero
> > timeout and backs off incrementally by increasing the timeout value on
> > subsequent iterations. The idea is to break up convoys and avoid big piles of
> > processes pounding on a spinlock. This cannot be done with sched_yield().
>
> Hard to beat the backoff argument. I vote we only use select().
I haven't heard any compelling arguments so far as to why
sched_yield() is better then select(), so I tend to vote the same way...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
В списке pgsql-hackers по дате отправления