Hi,

On Thu, Oct 1, 2026 at 3:30 PM Larry Garfield <[email protected]>
wrote:

> On Wed, Sep 30, 2026, at 12:57 PM, Jakub Zelenka wrote:
> > Hi,
> >
> > I would like to introduce the Polling API Additions RFC:
> >
> > https://wiki.php.net/rfc/poll_api_additions
> >
> > This is follow up to Polling API RFC.
> >
> > Kind regards,
> >
> > Jakub
>
> While much of these two RFCs is over my head, I will reiterate the same
> point I made to Tim and Derick.  You clearly have a roadmap in mind.  The
> RFCs hint at that, and discuss some parts of it.  But what's still missing
> is a single reference point with the full plan, at whatever level of
> granularity you have right now.  Please please put something like that
> together, probably on the Wiki someplace that the RFCs can reference.
>
> The work you're doing is incredibly important, and we really need to have
> a big picture view of the arc of your work so we can review it in the
> proper context.
>
>
If you are asking about a complete and detailed design doc for all 3 RFC's,
it can be found at
https://gist.github.com/bukka/87359261a4bfaa572ce43c93c0554b55 (I just
added a link to the RFC's).

There is really no roadmap except what is in those 3 RFC's (and more
details in that document). This particular RFC builds on existing Polling
API and introduces all bits that are needed to make it usable with IO Hooks
introduced in another RFC. The hooks RFC is all that is needed to allow
introduction of IO suspension points. The Ring RFC completes it with option
for IO offloading. There can be future implementation like Edmond's
scheduler that could make full use of this for the IO side of things. The
API was developed with this in mind but essentially it's an independent
project. The polling API additions are useful even without the IO Hooks as
those features are already requested by user space users of the API. If you
feel that some more details should be added to IO Hooks, please comment
there with a bit more specific info what exactly would you like to see
there.

Kind regards,

Jakub

Reply via email to