On 2017/01/03 17:40:04 -0800, Paul E. McKenney wrote:
> 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@xxxxxxxxx>
>> 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().
I see your point. Using \tco{} for API names should work.
A patch set follows.
In preparing this, I also found a long-lived typo in Table "Memory Barrier
Example 3". Patch 2 fixes it.
>
> Thanx, Paul
>
[snip]
--
Akira Yokosawa (2):
Use \tco{} for API names inside of tables
Fix typo smb_wmb() -> smp_wmb()
advsync/memorybarriers.tex | 20 ++++++++++----------
appendix/whymb/whymemorybarriers.tex | 14 +++++++-------
2 files changed, 17 insertions(+), 17 deletions(-)
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
