Yes, you‘ve hit the nail on the head - the Solaris port event framework is
meant to be a more efficient substitute for semaphores and polling event
completion. Sadly, its documentation leaves something to be desired.
Actually, I was wondering whether it’s possible to figure out who is posting
whom by looking into the port event function parameters. In doing so, I didn‘t
have any particular problem in mind, I was rather doing it just for fun, so to
Meanwhile, I watched Tanel Porder‘s hacking session recording
and learned that the message exchange between processes is being captured in
x$trace. Of course, this is a much better place to look for this kind of
information than analyzing low level OS calls.
Von meinem iPad gesendet
Am 14.04.2018 um 16:51 schrieb Frits Hoogland <frits.hoogland@xxxxxxxxx>:
I am not familiar with these functions.
It seems this port event framework is a solaris only thing, used as a
substitute for semaphores, obviously because oracle thinks they have better
performance or scale better. (actually they seem to say it’s mostly a
substitute for polling event completion).
There are multiple blogposts explaining them, telling essentially that.
What is it that you need to know?
port_send_event seems to send something, the address is probably a pointer to
a struct, and I am quite sure a foreground that has committed is the receiver
of it, because that is what the function of sskgpwpost does.
So that would be equivalent of semop on linux, posting the semaphore on which
a foreground is sleeping, waiting for the logwriter to get notified the redo
write has finished.
I don’t know the port event framework, but if you look at what happens when
multiple processes need posting on a semaphore on linux, another function
(sskgpwvectorpost) is executed and still all processes are posted serially,
maybe the event framework can post them all at once. Again, I don’t know the
port event framework, this might not be true, but this is the one of the
problems that the port event framework is documented to solve.
And the database implemented a solution for this already, which is “polling
mode”, which doesn’t require any communication from the logwriter to a
waiting foreground after writing, because the foreground checks writing
Mobile: +31 6 14180860
On 12 Apr 2018, at 10:39, Noveljic Nenad <nenad.noveljic@xxxxxxxxxxxx> wrote:
Is somebody familiar with the specification of Oracle Solaris kernel
functions portfs and port_send_event?
These functions are a part of the Solaris Event Completion framework. This
framework seems to be used instead of semaphores for posting messages
between processes on the Solaris implementation of Oracle.
Here is an example of a call stack within the lgwr process:
While the other port_* functions are well documented (see
) these two are completely missing despite being heavily used.
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee
you should in particular not disseminate, distribute, modify or copy this
e-mail. Please notify the sender immediately by e-mail, if you have received
this message by mistake and delete it from your system.
E-mail transmission may not be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of the
Vontobel Group and its affiliates for any damages resulting from e-mail use
is excluded. You are advised that urgent and time sensitive messages should
not be sent by e-mail and if verification is required please request a