From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 00/13] Remove \co{} commands in tables
Date: Tue, 3 Jan 2017 17:40:04 -0800 [thread overview]
Message-ID: <20170104014004.GG3742@linux.vnet.ibm.com> (raw)
In-Reply-To: <a054d07b-3b69-25ce-aab4-c294dc3b6bcd@gmail.com>
On Wed, Jan 04, 2017 at 10:15:40AM +0900, Akira Yokosawa wrote:
> >From d07bf0df57c597c22de9a7c159f10b0247cea8c2 Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Wed, 4 Jan 2017 08:51:15 +0900
> Subject: [PATCH 00/13] Remove \co{} commands in tables
>
> \co{} command confuses column width estimation of tabular environment.
> By removing \co{} commands in tables, bogus "~"s for manual width
> adjustment can be removed.
>
> Patch 1 introduces an alternative command \tco{} to be used in tables.
> Patches 2--8 remove \co{} commands by using \tco{} or removing unnecessary
> commands.
> Patch 9 removes another "~" and uses \vspace{} instead.
> Patches 10--13 do additional font tweaks. It looks better for me if
> headers of tables such as "Thread 1" and "CPU 1" are typeset in normal font
> of the text (Times Roman). Patch 13, which tweaks font of non-code words in
> table, may be an excessive tweak. Whether or not to apply it is up to the
> editor.
I queued and pushed these, thank you!
I am a little concerned about the added "\_" instances that show up
in some of the tables, though. Does it work to use \tco{} or similar
to avoid these? My concern is frustration for people searching the
.tex source for tables containing (say) smp_wmb().
Thanx, Paul
> --
> Akira Yokosawa (13):
> Define \tco{} command to be used in table
> rcufundamental: Rewrite table 'RCU Publish and Subscribe Primitives'
> rcuapi: Rewrite table 'RCU Wait-to-Finish APIs'
> rcuapi: Rewrite table 'RCU Publish-Subscribe and Version Maintenance
> APIs'
> whichtochoose: Rewrite table 'Which Deferred Technique to Choose?'
> memorybarriers: Remove \co{} in tabular env
> memorybarriers: Use \verb in table 'Lock-Based Critical Sections'
> whymemorybarriers: Remove \co{} in tabular env
> memorybarriers: Replace nbsp with \vspace
> Add \nf{} command to go back to normal font
> memorybarriers: Add \nf{} command to table header
> whymemorybarriers: Add \nf{} command to table header
> memorybarriers: Add \nf{} command to descriptive words in table
>
> advsync/memorybarriers.tex | 187 +++++++++++++++++------------------
> appendix/whymb/whymemorybarriers.tex | 70 ++++++-------
> defer/rcuapi.tex | 110 +++++++++------------
> defer/rcufundamental.tex | 18 ++--
> defer/whichtochoose.tex | 20 ++--
> perfbook.tex | 6 +-
> 6 files changed, 200 insertions(+), 211 deletions(-)
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-01-04 1:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 1:15 [PATCH 00/13] Remove \co{} commands in tables Akira Yokosawa
2017-01-04 1:17 ` [PATCH 01/13] Define \tco{} command to be used in table Akira Yokosawa
2017-01-04 1:19 ` [PATCH 02/13] rcufundamental: Rewrite table 'RCU Publish and Subscribe Primitives' Akira Yokosawa
2017-01-04 1:20 ` [PATCH 03/13] rcuapi: Rewrite table 'RCU Wait-to-Finish APIs' Akira Yokosawa
2017-01-04 1:21 ` [PATCH 04/13] rcuapi: Rewrite table 'RCU Publish-Subscribe and Version Maintenance APIs' Akira Yokosawa
2017-01-04 1:23 ` [PATCH 05/13] whichtochoose: Rewrite table 'Which Deferred Technique to Choose?' Akira Yokosawa
2017-01-04 1:24 ` [PATCH 06/13] memorybarriers: Remove \co{} in tabular env Akira Yokosawa
2017-01-04 1:25 ` [PATCH 07/13] memorybarriers: Use \verb in table 'Lock-Based Critical Sections' Akira Yokosawa
2017-01-04 1:26 ` [PATCH 08/13] whymemorybarriers: Remove \co{} in tabular env Akira Yokosawa
2017-01-04 1:28 ` [PATCH 09/13] memorybarriers: Replace nbsp with \vspace Akira Yokosawa
2017-01-04 1:29 ` [PATCH 10/13] Add \nf{} command to go back to normal font Akira Yokosawa
2017-01-04 1:30 ` [PATCH 11/13] memorybarriers: Add \nf{} command to table header Akira Yokosawa
2017-01-04 1:31 ` [PATCH 12/13] whymemorybarriers: " Akira Yokosawa
2017-01-04 1:32 ` [PATCH 13/13] memorybarriers: Add \nf{} command to descriptive words in table Akira Yokosawa
2017-01-04 1:40 ` Paul E. McKenney [this message]
2017-01-04 11:35 ` [PATCH 0/2] Use \tco{} for API names inside of tables Akira Yokosawa
2017-01-04 11:36 ` [PATCH 1/2] " Akira Yokosawa
2017-01-04 11:37 ` [PATCH 2/2] Fix typo smb_wmb() -> smp_wmb() Akira Yokosawa
2017-01-04 16:28 ` [PATCH 0/2] Use \tco{} for API names inside of tables Paul E. McKenney
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=20170104014004.GG3742@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.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