Re: Interrupts vs signals

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Interrupts vs signals
Date: 2024-11-15 14:24:37
Message-ID: c3e9de97-6073-47bf-8580-0435ed702bab@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Here is also a version of Thomas's "Use Latch for bgworker state change
notification patch", rebased over the "Replace latches with Interrupts"
patch.

I used INTERRUPT_GENERAL_WAKEUP for the notification, as a
straightforward replacement of setting the latch, but I wonder if we
should have a dedicated interrupt flag for this instead.

--
Heikki Linnakangas
Neon (https://neon.tech)

Attachment Content-Type Size
v4-0003-Use-proc-interrupt-for-bgworker-state-change-noti.patch text/x-patch 23.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2024-11-15 14:32:17 Re: Potential ABI breakage in upcoming minor releases
Previous Message Rahila Syed 2024-11-15 13:58:51 Re: Enhancing Memory Context Statistics Reporting