From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/5] Update table layout
Date: Wed, 25 Oct 2017 12:19:13 -0700 [thread overview]
Message-ID: <20171025191913.GO3659@linux.vnet.ibm.com> (raw)
In-Reply-To: <e21a5aaa-23a8-16a9-ad10-aa08188465b6@gmail.com>
On Tue, Oct 24, 2017 at 10:50:44PM +0900, Akira Yokosawa wrote:
> On 2017/10/23 10:49:56 -0700, Paul E. McKenney wrote:
> > On Tue, Oct 24, 2017 at 12:25:20AM +0900, Akira Yokosawa wrote:
> >> On 2017/10/22 19:24:30 -0700, Paul E. McKenney wrote:
> >>> On Mon, Oct 23, 2017 at 12:20:14AM +0900, Akira Yokosawa wrote:
> >>>> >From d224db4bfed5d4ce0639062a920bafc6f9442e16 Mon Sep 17 00:00:00 2001
> >>>> From: Akira Yokosawa <akiyks@gmail.com>
> >>>> Date: Sun, 22 Oct 2017 23:55:49 +0900
> >>>> Subject: [PATCH 0/5] Update table layout
> >>>>
> >>>> Hi Paul,
> >>>>
> >>>> My first idea was to add a make target for "table captions at the top".
> >>>> But I changed my mind and promoted the layout as default.
> >>>> Instead, I added a target "perfbook-tcb.pdf" (tcb: Table Caption Bottom),
> >>>> which keeps the caption at the bottom.
> >>>>
> >>>> Patch #1 does the change in perfbook.tex and Makefile.
> >>>>
> >>>> Patches #2 and #3 are minor fixes I noticed while updating tables.
> >>>>
> >>>> Patch #4 updates most tables to use the new table layout experimented in
> >>>> Style Guide for a while. It contains changes to use "S" column specifier
> >>>> provided by the "siunitx" package.
> >>>>
> >>>> Patch #5 converts a table into a figure drawn by tabular.
> >>>>
> >>>> There remains several tables not yet touched. They are complex and large
> >>>> ones. They need extra work to use the new scheme.
> >>>>
> >>>> NOTE: Table 13.1 does not contain legends and does not use subscripts
> >>>> as shown in Table D.5 at the moment. In the text, it looks OK to me.
> >>>>
> >>>> Thoughts?
> >>>
> >>> At a first scan, this all looks good. There are a few remaining
> >>> tables in the old format, including a couple that we discussed earlier
> >>> as being quite complex. Which should be fine, for the time being,
> >>> at least. But what are your thoughts on the remaining old-style tables?
> >>
> >> Tables 17.1 and 17.2 are hard ones. Alternate-row coloring scheme can not
> >> be applied for them. We need to figure out how to improve them. I'm fine with
> >> them to be left for the moment.
> >
> > Works for me as well!
> >
> >> Table 7.1 does not fit to the format because of the "Null (Not Held)" column.
> >> As all the cells of the column are all blank, vertical rules actually helps
> >> in this table. If you put some character/symbol to indicate compatibility,
> >> it can be converted to the new format. If you have a good candidate, please
> >> let me know.
> >
> > Hmmm... Is there a very light grey variant of the square that appears
> > at the end of each quick quiz? "\rule{7pt}{7pt}}", if I am not getting
> > too confused. Ah, there is. Please see the crude experimental patch
> > below. (As in if you do choose to do something like this, please make
> > a more sensible/maintainable version.)
>
> So, I've just submitted a patch to do the format conversion.
> I'm not sure "\x" is the right name to use, but one character is convenient
> in this table. In this case, coloring alternate rows is not necessary.
Fair point! I must confess that I had hoped that you would come up with
a more clever way to do this, but is it possible to somehow undefine \x
immediately after use? Just to give better diagnostics for inadvertent
reuse...
> The following patch is to keep position of table captions consistent.
I am taking that one. I am on a plane right now, so it might be some
time before they show up outside of my laptop.
> Ah, there is another reminder for you.
> You need to mention the moved "advsync/rt" section in the outline of advsync
> chapter, don't you? Honestly speaking, it is not obvious at first glance
> how it relates to weaker synchronization.
I was thinking that there is more than one way to "advance" synchronization,
but agreed, I do need to make this clear.
> A good introduction should help readers.
I took a shot at this and pushed it out. Thoughts?
Thanx, Paul
next prev parent reply other threads:[~2017-10-25 19:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 15:20 [PATCH 0/5] Update table layout Akira Yokosawa
2017-10-22 15:22 ` [PATCH 1/5] Move caption of table to top Akira Yokosawa
2017-10-22 15:24 ` [PATCH 2/5] Define \twocolumnwidth for 1c layout Akira Yokosawa
2017-10-22 15:25 ` [PATCH 3/5] Use \O{} macro for 'order-of' Akira Yokosawa
2017-10-22 15:26 ` [PATCH 4/5] Update tables using booktabs and alternate-row coloring scheme Akira Yokosawa
2017-10-22 15:28 ` [PATCH 5/5] datastruct: Convert 'NUMA Topology of System Under Test' to figure Akira Yokosawa
2017-10-23 2:24 ` [PATCH 0/5] Update table layout Paul E. McKenney
2017-10-23 15:25 ` Akira Yokosawa
2017-10-23 17:49 ` Paul E. McKenney
2017-10-24 13:50 ` Akira Yokosawa
2017-10-25 19:19 ` Paul E. McKenney [this message]
2017-10-23 15:27 ` [PATCH 1/3] whymb: " Akira Yokosawa
2017-10-23 15:29 ` [PATCH 2/3] defer/rcuapi: " Akira Yokosawa
2017-10-23 15:30 ` [PATCH 3/3] Convert table of code fragments to 'listing' Akira Yokosawa
2017-10-23 18:00 ` [PATCH 1/3] whymb: Update table layout 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=20171025191913.GO3659@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.