Re: GNU/Hurd portability patches

From: Michael Banck <mbanck(at)gmx(dot)net>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Samuel Thibault <samuel(dot)thibault(at)gnu(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: GNU/Hurd portability patches
Date: 2025-11-17 09:39:56
Message-ID: 20251117093955.GB8364@p46.dedyn.io;lightning.p46.dedyn.io
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Thomas,

On Mon, Nov 17, 2025 at 03:59:30PM +1300, Thomas Munro wrote:
> On Tue, Nov 11, 2025 at 10:49 AM Michael Banck <mbanck(at)gmx(dot)net> wrote:
> > |login: task ./test_signalhandler(767) looked up a bogus port 23 for3205, most probably a bug.
>
> . o O { An absurdly far-fetched thought while browsing glibc/hurd glue
> code: if synchronous I/O is implemented as RPC on Mach ports, could
> that mean that it's technically possible to submit now and consume
> results later, for asynchronous I/O? Possibly too
> private/undocumented anyway, and maybe they'll eventually do io_uring
> or something... I idly wondered about driving I/O directly with ports
> while studying the dismal implementation of POSIX AIO on macOS, which
> also derives from CMU Mach, but NeXT/Apple jammed file systems down
> into the unikernel part behind traditional syscalls, and it looks like
> maybe only raw devices are accessible with ports. (I have dim
> memories of learning C and assembler more than 30 years ago on a
> Commodore Amiga whose microkernel nee Cambridge TRIPOS worked like
> that... that cheap home computer could easily get both floppy drives
> doing random I/O at once while computing other stuff, unlike Unix...)
> }

I have CC'd Samuel Thibault who is the currently active Hurd committer/
maintainer, I hope he can comment on that.

Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-11-17 09:48:43 quoteOneName() inconsistency with quote_all_identifiers — replacement API proposed
Previous Message Michael Banck 2025-11-17 09:35:59 Re: Dead code in ps_status.c