Re: Spinlocks and compiler/memory barriers

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Spinlocks and compiler/memory barriers
Дата
Msg-id 20140630222854.GW26930@awork2.anarazel.de
обсуждение исходный текст
Ответ на Re: Spinlocks and compiler/memory barriers  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: Spinlocks and compiler/memory barriers  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On 2014-06-30 19:22:59 +0200, Andres Freund wrote:
> On 2014-06-30 12:46:29 -0400, Robert Haas wrote:
> >, which if I understand you correctly are ARM without GCC
> > atomics, Sparc, and MIPS.
>
> I've to revise my statement on MIPS, it actually looks safe. I seem to
> have missed that it has its own S_UNLOCK.

So, here's my first blind attempt at fixing these. Too tired to think
much more about it. Sparc's configurable cache coherency drives me
nuts. Linux apparently switched somewhere in 2011 from RMO (relaxed
memory order) to TSO (total store order), solaris always used TSO, but
the BSDs don't. Man.

Accordingly there's a somewhat ugly thingy attached. I don't think this
is really ready, but it's what I can come up today.

Greetings,

Andres Freund

--
 Andres Freund                       http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Fujii Masao
Дата:
Сообщение: Re: WAL format and API changes (9.5)
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: bad estimation together with large work_mem generates terrible slow hash joins