Re: Blocking I/O, async I/O and io_uring

From: Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robert(dot)haas(at)enterprisedb(dot)com>, Petr Jelinek <petr(dot)jelinek(at)enterprisedb(dot)com>
Subject: Re: Blocking I/O, async I/O and io_uring
Date: 2020-12-08 03:00:30
Message-ID: CAGRY4nxbp4uTZ5DOt6SaA66wcGQcnVpxhk4etNix4gGV-NdSrg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

References to get things started:

* https://lwn.net/Articles/810414/
* https://unixism.net/loti/what_is_io_uring.html
*
https://blogs.oracle.com/linux/an-introduction-to-the-io_uring-asynchronous-io-framework
*
https://thenewstack.io/how-io_uring-and-ebpf-will-revolutionize-programming-in-linux/

You'll probably notice how this parallels my sporadic activities around
pipelining in other areas, and the PoC libpq pipelining patch I sent in a
few years ago.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2020-12-08 03:04:04 Re: Huge memory consumption on partitioned table with FKs
Previous Message Craig Ringer 2020-12-08 02:55:37 Blocking I/O, async I/O and io_uring