From: "Paul E. McKenney" <paulmck@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Leonardo Bras <leobras.c@gmail.com>, perfbook@vger.kernel.org
Subject: Re: [PATCH -perfbook 0/4] cpu/overheads: Make tables more consistent
Date: Tue, 14 Feb 2023 15:13:15 -0800 [thread overview]
Message-ID: <20230214231315.GH2948950@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <8f565979-bba0-bab1-7c8e-ebc76c2b4e65@gmail.com>
On Tue, Feb 14, 2023 at 07:03:12PM +0900, Akira Yokosawa wrote:
> Hi,
>
> This patch set is a follow-up to commit 34cc066b1d95 ("cpu: Add a QQz
> on table E.1").
>
> Leo posted a patch to improve Table E.1 at [1].
>
> I have gone further to improve consistency among tables on overheads
> of atomic operations.
>
> Patch 1/4 changes the layout of those tables and adjusts upper-/
> lower-casing (with Reported-by: from Leo).
>
> I found the use of "In-Core" and "Off-Core" in the tables somewhat
> strange. Usually, I find pairs of "On/Off" and "In/Out" more natural.
> In overheads.tex, "On-Core" vs "Off-Core" looks better to me.
>
> So Patch 2/4 replaces "in-core" with "on-core", and does similar
> replacements.
>
> Patch 3/4 adds a page reference in QQz 3.8.
>
> Patch 4/4 is an independent change fixing an issue in -nq builds.
> I noticed an extra "," in the anchor box containing QQz 4.20, 4.21,
> and 4.22 while skimming through QQz's in those builds.
>
> [1]: https://www.spinics.net/lists/perfbook/msg03827.html
Queued and pushed, thank you!
Thanx, Paul
> Thanks, Akira
> --
> Akira Yokosawa (4):
> cpu: Improve layout and consistency of Tables 3.1, E.1, and E.2
> cpu: Use 'on-core' rather than 'in-core'
> cpu: Add page reference to Table E.1 in QQz 3.8
> toolsoftrade: Fix QQz macro in QQz series
>
> cpu/overheads.tex | 161 +++++++++++++++++++++-------------
> perfbook-lt.tex | 6 ++
> toolsoftrade/toolsoftrade.tex | 2 +-
> 3 files changed, 108 insertions(+), 61 deletions(-)
>
>
> base-commit: 50bb4adf51f683ba2c7d90f269632b6f4b4d4704
> --
> 2.25.1
>
prev parent reply other threads:[~2023-02-14 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 10:03 [PATCH -perfbook 0/4] cpu/overheads: Make tables more consistent Akira Yokosawa
2023-02-14 10:05 ` [PATCH -perfbook 1/4] cpu: Improve layout and consistency of Tables 3.1, E.1, and E.2 Akira Yokosawa
2023-02-14 10:07 ` [PATCH -perfbook 2/4] cpu: Use 'on-core' rather than 'in-core' Akira Yokosawa
2023-02-14 10:08 ` [PATCH -perfbook 3/4] cpu: Add page reference to Table E.1 in QQz 3.8 Akira Yokosawa
2023-02-14 10:09 ` [PATCH -perfbook 4/4] toolsoftrade: Fix QQz macro in QQz series Akira Yokosawa
2023-02-14 23:13 ` Paul E. McKenney [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=20230214231315.GH2948950@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=leobras.c@gmail.com \
--cc=perfbook@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).