Re: [RFC PATCH] Documentation/rv: Explain epoll and aborted sleeps
Chao Liu <[email protected]> Sat, 25 Jul 2026 00:17:45 +0800
| Newsgroups | org.kernel.vger.linux-trace-kernel,org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Jul 25, 2026 at 12:00:06AM +0800, Chao Liu wrote: > Results > ------- > > The first two rows compare arm64 without and with the experimental > mapping. The x86_64 row is the unmodified cross-check using its native > `__NR_epoll_wait`. The arm64 rows enter through `epoll_pwait`. > > Each case was run five times. `M [L-H]` means median To correct the ambiguity of my last email (sorry for the trouble): the data in each entry is formatted as M[L-H]. For example, in the second column of "Ep abort": 26 [20-28]. > `[minimum-maximum]`; a single value means all five runs had that result. > > +----------------+------------------+------------+---------------+--------+ > | Case | P1 err | Ep abort | PI block | P2 err | > +----------------+------------------+------------+---------------+--------+ > | arm64 baseline | 2043 [2031-2047] | 0 | 0 | 1 | > | arm64 mapping | 0 | 26 [20-28] | 355 [308-399] | 1 | > | x86_64 native | 0 | 31 [25-92] | 201 [147-204] | 1 | > +----------------+------------------+------------+---------------+--------+ > Thanks, Chao