Skip site navigation (1) Skip section navigation (2)

Re: sched_yield()

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: scrappy(at)hub(dot)org (The Hermit Hacker)
Cc: matti(at)algonet(dot)se, dz(at)cs(dot)unitn(dot)it, hackers(at)postgreSQL(dot)org
Subject: Re: sched_yield()
Date: 1998-03-22 03:59:03
Message-ID: 199803220359.WAA02341@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
> 
> 	You missed my point...so far as I've heard, there are two ways of
> doing what is being proposed...either using sched_yield() on those systems
> that support it, or select() on those that don't.  If you are going to
> build a patch for this, it should look something like:
> 
> #ifdef HAVE_SCHED_YIELD
> 	<insert sched_yield() code here>
> #else
> 	<insert select() code here>
> #endif
> 
> 	Totally 'configure' configurable, and non-system dependent :)

Yep, I like it.

-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

In response to

pgsql-hackers by date

Next:From: The Hermit HackerDate: 1998-03-22 04:00:01
Subject: Re: [HACKERS] Re: sched_yield()
Previous:From: Bruce MomjianDate: 1998-03-22 03:58:03
Subject: Re: [HACKERS] patch for memory overrun on Linux(i386)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group