| From: | Manfred Spraul <manfred(at)colorfullife(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <JanWieck(at)Yahoo(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 15:17:10 |
| Message-ID: | 3FF196F6.90500@colorfullife.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2003-12-30 15:28:37 | Re: [PATCHES] update i386 spinlock for hyperthreading |
| Previous Message | Jeff Eckermann | 2003-12-30 14:58:25 | Re: [pgsql-advocacy] Is my MySQL Gaining ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2003-12-30 15:28:37 | Re: [PATCHES] update i386 spinlock for hyperthreading |
| Previous Message | Jeff Eckermann | 2003-12-30 14:58:25 | Re: [pgsql-advocacy] Is my MySQL Gaining ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2003-12-30 15:28:37 | Re: [PATCHES] update i386 spinlock for hyperthreading |
| Previous Message | Bruce Momjian | 2003-12-30 14:56:04 | Re: [PATCHES] update i386 spinlock for hyperthreading |