From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/4] formal/spinhint: Clarify hashtable sizes used in tables
Date: Tue, 12 Feb 2019 08:38:40 -0800 [thread overview]
Message-ID: <20190212163840.GN4240@linux.ibm.com> (raw)
In-Reply-To: <1b7c8489-cf0a-d959-f307-e3eadae4998c@gmail.com>
On Wed, Feb 13, 2019 at 12:31:22AM +0900, Akira Yokosawa wrote:
> Hi Paul,
>
> In your wordsmithing, there was confusion of hashtable sizes used in
> Tables 12.2 and 12.3. Patch #1 attempts to clarify the point. It also
> adds a footnote and fixes a few trivial typos.
>
> Patch #2 is a minor tweak to use "lmtt" font for code snippets
> imported by \VerbatimInput{} command. This fixes font of Listing 12.3
> for experimental targets such as "msnt" and "1csf".
>
> Patch #3 fixes font choice of snippets in experimental targets "msns"
> (original monospace font of "courier") and "mss" (previous monospace
> font choice of "scaled courier"), which have kept using those fonts for code
> snippets. As is mentioned in the change log, there are a lot of overfills
> in code snippets. On the other hand, the font used in the target "msn"
> (monospace narrow) is narrower than the "lmtt" font and it should be OK
> to use it in code snippets.
>
> Patch #4 resolves the warning from "make" due to a stray litmus test
> "C-SB+o-rcusync-o+rl-rul-o.litmus". My guess is that this file was
> unintentionally sneaked into the repository in commit 4a6337b85633
> ("memorder: Cover litmus tests for accesses outside of RCU readers").
> But you may have an idea what the test of that name should look like.
> If this is the case, please update the test instead of applying this
> patch.
I applied #1 with tweaks and #2 and #3 as is. I am holding off on #4
for the moment because it looks to me that it is being used. So please
check my tweaks to #1 and my reasoning on #4.
Thanx, Paul
> Thanks, Akira
> --
> Akira Yokosawa (4):
> formal/spinhint: Clarify hashtable sizes used in Tables 12.2 and 12.3
> Set default fontfamily for snippets of 'fancyvrb'
> Change monospace font of snippets for targets 'mss', 'msns', and 'msn'
> memorder: Remove 'snippet' meta command in stray litmus test
>
> CodeSamples/formal/herd/C-SB+o-rcusync-o+rl-rul-o.litmus | 2 --
> Makefile | 11 +++++------
> formal/spinhint.tex | 14 ++++++++------
> perfbook.tex | 5 +----
> 4 files changed, 14 insertions(+), 18 deletions(-)
>
> --
> 2.7.4
>
prev parent reply other threads:[~2019-02-12 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 15:31 [PATCH 0/4] formal/spinhint: Clarify hashtable sizes used in tables Akira Yokosawa
2019-02-12 15:33 ` [PATCH 1/4] formal/spinhint: Clarify hashtable sizes used in Tables 12.2 and 12.3 Akira Yokosawa
2019-02-12 15:35 ` [PATCH 2/4] Set default fontfamily for snippets of 'fancyvrb' Akira Yokosawa
2019-02-12 15:37 ` [PATCH 3/4] Change monospace font of snippets for targets 'mss', 'msns', and 'msn' Akira Yokosawa
2019-02-12 15:39 ` [PATCH 4/4] memorder: Remove 'snippet' meta command in stray litmus test Akira Yokosawa
2019-02-12 16:16 ` Paul E. McKenney
2019-02-12 22:11 ` Akira Yokosawa
2019-02-12 23:45 ` Paul E. McKenney
2019-02-13 16:04 ` Paul E. McKenney
2019-02-12 16:38 ` 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=20190212163840.GN4240@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=akiyks@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