perfbook.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

From: Hao Lee <haolee.swjtu@gmail.com>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org
Subject: Does perfbook need some prior knowledge?
Date: Tue, 5 Apr 2022 21:52:23 +0800	[thread overview]
Message-ID: <CA+PpKPmTsMMP6n3hYEqNxav_qQcyFPmff0GwYCauyuHY7GDM3w@mail.gmail.com> (raw)

Hi, Paul

I'm currently reading perfbook, but I often get stuck in some concepts
which are not explained. Does this book need some prior knowledge?
Or all these concepts are explained later and I just need to keep
reading patiently?

For example, on page 67 in v2021.12.22a:

    For example, a write memory barrier (Linux kernel smp_wmb()) would
    order the store, but not the load. This situation might suggest use
    of smp_store_release() over smp_wmb().

Unfortunately, although I have some knowledge about Linux kernel, I'm not
familiar with the concepts such as store_release, smp_wmb, etc. I don't
know if I should keep reading this book until all these concepts are
explained or stop reading the book and learn some prior knowledge.

Thanks,
Hao Lee

next             reply	other threads:[~2022-04-05 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 13:52 Hao Lee [this message]
2022-04-05 15:31 ` Does perfbook need some prior knowledge? Paul E. McKenney
2022-04-06  3:05   ` Hao Lee
2022-04-07 15:29   ` Akira Yokosawa
2022-04-07 16:41     ` Paul E. McKenney
2022-04-07 23:18       ` Akira Yokosawa
2022-04-08  1:45         ` Paul E. McKenney
2022-04-08  8:49           ` Hao Lee
2022-04-19 17:46             ` Paul E. McKenney
2022-04-20 11:57               ` Hao Lee

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=CA+PpKPmTsMMP6n3hYEqNxav_qQcyFPmff0GwYCauyuHY7GDM3w@mail.gmail.com \
    --to=haolee.swjtu@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

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).