From: Chao Liu <chao.liu@processmission.com>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: Nam Cao <namcao@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Jonathan Corbet <corbet@lwn.net>,
lianux.mm@gmail.com, lianux.wang@processmission.com,
Shuah Khan <skhan@linuxfoundation.org>,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] Documentation/rv: Explain epoll and aborted sleeps
Date: Sat, 25 Jul 2026 00:17:45 +0800 [thread overview]
Message-ID: <amOOoorD5IXKKsxk@ChaodeMacBook-Pro.local> (raw)
In-Reply-To: <amNlh-GZO-RcbpiL@ChaodeMacBook-Pro.local>
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
prev parent reply other threads:[~2026-07-24 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 4:57 [RFC PATCH] Documentation/rv: Explain epoll and aborted sleeps Chao Liu
2026-07-24 7:20 ` Gabriele Monaco
2026-07-24 15:59 ` Chao Liu
2026-07-24 16:17 ` Chao Liu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=amOOoorD5IXKKsxk@ChaodeMacBook-Pro.local \
--to=chao.liu@processmission.com \
--cc=corbet@lwn.net \
--cc=gmonaco@redhat.com \
--cc=lianux.mm@gmail.com \
--cc=lianux.wang@processmission.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox