Re: Spinlocks, yet again: analysis and proposed patches

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Marko Kreen <marko(at)l-t(dot)ee>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Spinlocks, yet again: analysis and proposed patches
Date: 2005-09-13 13:47:46
Message-ID: 87hdcp13lp.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marko Kreen <marko(at)l-t(dot)ee> writes:

> > (I speculate that it's set up to only yield the processor to other
> > processes already affiliated to that processor. In any case, it
> > is definitely capable of getting through 10000 yields without
> > running the guy who's holding the spinlock.)

Maybe it should try sched_yield once and then use select after that?

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2005-09-13 13:47:54 Re: Hard drive failure leads to corrupt db
Previous Message Michael Paesold 2005-09-13 13:41:22 Bug with cursor declaration in PL/pgSQL in CVS tip?