Re: [PATCHES] update i386 spinlock for hyperthreading - Mailing list pgsql-hackers

From Manfred Spraul
Subject Re: [PATCHES] update i386 spinlock for hyperthreading
Date
Msg-id 3FF196F6.90500@colorfullife.com
Whole thread Raw
In response to Re: [PATCHES] update i386 spinlock for hyperthreading  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [PATCHES] update i386 spinlock for hyperthreading  (Jan Wieck <JanWieck@Yahoo.com>)
List pgsql-hackers
Bruce Momjian wrote:

>>Anyone see an attack path here?
>>    
>>
>
>Should we have one lock per hash bucket rather than one for the entire
>hash?
>  
>
That's the simple part. The problem is the aging strategy: we need a
strategy that doesn't rely on a global list that's updated after every
lookup. If I understand the ARC code correctly, there is a
STRAT_MRU_INSERT(cdb, STRAT_LIST_T2) that happen in every lookup.


--
Manfred




pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] update i386 spinlock for hyperthreading
Next
From: Andrew Dunstan
Date:
Subject: select() for small sleep