Re: [PATCHES] update i386 spinlock for hyperthreading

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Manfred Spraul <manfred(at)colorfullife(dot)com>, pgsql-hackers(at)postgreSQL(dot)org, markw(at)osdl(dot)org
Subject: Re: [PATCHES] update i386 spinlock for hyperthreading
Date: 2003-12-30 05:33:16
Message-ID: 3FF10E1C.7050304@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-patches

Tom Lane wrote:

>Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>
>
>>Manfred Spraul wrote:
>>
>>
>>>I remember there were patches that tried other algorithms instead of the
>>>simple LRU for the buffer manager. Has anyone tried to change the
>>>locking of the buffer manager?
>>>
>>>
>
>
>
>>CVS HEAD already has an Adaptive Replacement Cache (ARC) for buffer
>>replacement.
>>
>>
>
>That's irrelevant to the problem, though. Unless the ARC code uses data
>structures that are more amenable to localized locking than the old
>global buffer freelist. (Jan?)
>
> regards, tom lane
>
>

Not that I know of. The new strategy uses one shared hash table like the
old, and one buffer pool as well. It grabs the same old Bufmgr lock
during the lookup+replacement decision process, gives it up during
eventual IO, grabs it again when done with the IO. As a matter of fact,
the strategy itself does no locking at all. Like the old LRU code it
simply assumes that the buffer manager holds the lock during calls.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-12-30 05:41:30 Re: [PATCHES] update i386 spinlock for hyperthreading
Previous Message Grant Allen 2003-12-30 05:26:38 Re: Any way to disable backslash as a string literal escape character?

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-12-30 05:41:30 Re: [PATCHES] update i386 spinlock for hyperthreading
Previous Message Bret Busby 2003-12-30 04:56:19 Re: Is my MySQL Gaining ?

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2003-12-30 05:41:30 Re: [PATCHES] update i386 spinlock for hyperthreading
Previous Message Tom Lane 2003-12-30 04:14:48 Re: [PATCHES] update i386 spinlock for hyperthreading