From: Zhouyi Zhou <zhouzhouyi@gmail.com>
To: paulmck@kernel.org
Cc: akiyks@gmail.com, perfbook@vger.kernel.org
Subject: Re: [PATCH -perfbook] cpu: make Quick Quiz 3.6 more explicit
Date: Sat, 30 Dec 2023 07:56:50 +0800 [thread overview]
Message-ID: <CAABZP2wzPWy07CHeRS+aL9HZ6Hc8SMJOOvetaGzeDtTnRe7KPg@mail.gmail.com> (raw)
In-Reply-To: <6bbba502-bb0b-42fa-a77a-f86cee8f93c3@paulmck-laptop>
On Sat, Dec 30, 2023 at 7:22 AM Paul E. McKenney <paulmck@kernel.org> wrote:
>
> On Sat, Dec 30, 2023 at 07:15:56AM +0800, Zhouyi Zhou wrote:
> > On Sat, Dec 30, 2023 at 7:09 AM Paul E. McKenney <paulmck@kernel.org> wrote:
> > >
> > > On Thu, Dec 28, 2023 at 11:55:00AM +0800, zhouzhouyi@gmail.com wrote:
> > > > From: Zhouyi Zhou <zhouzhouyi@gmail.com>
> > > >
> > > > Rewrite Quick Quiz 3.6 for clarity and explicitness, so that the
> > > > firsttime reader know that another choice is CPU 0 sharing a core
> > > > with CPU 1.
> > > >
> > > > Signed-off-by: Zhouyi Zhou<zhouzhouyi@gmail.com>
> > > > ---
> > > > hi Paul and Akira
> > > >
> > > > This minor fix is also reported by our Chinese version editor
> > > > Yunjing Li.
> > >
> > > I have pulled this in, thanks to both you and the editor! Would it be
> > > appropriate to have the editor's reported-by? (I trust your judgment
> > > on this. I am only asking, not in any way suggesting a change.)
> > I think I should have the editor's report-by, but she is too modest to
> > offer her email-address,
> > because she thinks this is her job.
> >
> > Could we add reported-by without an email address ? ;-)
>
> We could just add a line saying something like:
>
> This change was identified by XXX YYYYY in the course of
> translating the book to Chinese.
>
> Or something similar. What would our editor like best?
>
> For another option, I do sometimes do "Reported-by: LWN user xxxx"
> or similar.
Thank Paul for your wonderful suggestion!
I guess our editor will like the first option best ;-)
I will send a new version of patch soon.
Thanks, Paul
>
> Thanx, Paul
>
> > Thanx, Zhouyi
> > >
> > > Thanx, Paul
> > >
> > > > Thanks
> > > > Zhouyi
> > > > --
> > > > cpu/overheads.tex | 3 ++-
> > > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/cpu/overheads.tex b/cpu/overheads.tex
> > > > index 1ee9c52f..a2ec2998 100644
> > > > --- a/cpu/overheads.tex
> > > > +++ b/cpu/overheads.tex
> > > > @@ -262,7 +262,8 @@ CAS and lock, respectively.
> > > > \QuickQuiz{
> > > > \Cref{tab:cpu:CPU 0 View of Synchronization Mechanisms on 8-Socket System With Intel Xeon Platinum 8176 CPUs at 2.10GHz}
> > > > shows CPU~0 sharing a core with CPU~224.
> > > > - Shouldn't that instead be CPU~1???
> > > > + However, isn't it more logical for CPU 0
> > > > + to share a core with CPU 1 instead of CPU 224???
> > > > }\QuickQuizAnswer{
> > > > It is easy to be sympathetic to this view, but the file
> > > > \path{/sys/devices/system/cpu/cpu0/cache/index0/shared_cpu_list}
> > > > --
> > > > 2.34.1
> > > >
> >
prev parent reply other threads:[~2023-12-29 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 3:55 [PATCH -perfbook] cpu: make Quick Quiz 3.6 more explicit zhouzhouyi
2023-12-29 23:09 ` Paul E. McKenney
2023-12-29 23:15 ` Zhouyi Zhou
2023-12-29 23:22 ` Paul E. McKenney
2023-12-29 23:56 ` Zhouyi Zhou [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=CAABZP2wzPWy07CHeRS+aL9HZ6Hc8SMJOOvetaGzeDtTnRe7KPg@mail.gmail.com \
--to=zhouzhouyi@gmail.com \
--cc=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--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).