From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Junchang Wang <junchangwang@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: Question about performance figures in Section 9
Date: Sun, 14 May 2017 09:33:47 -0700 [thread overview]
Message-ID: <20170514163347.GO3956@linux.vnet.ibm.com> (raw)
In-Reply-To: <CABoNC812ZneaAkQ7EERgcz6y3OOaY+03ybNfX_0jYxZ2Fed2BQ@mail.gmail.com>
On Sun, May 14, 2017 at 11:02:18PM +0800, Junchang Wang wrote:
> Hi list,
>
> I'm reading Section 9 which is excellent. I have one quick question
> now. For performance figures (e.g. 9.16 on page 178), what's the
> pattern of add/del being performed? Are we assuming a mostly read
> rarely write scenario? I'm totally fine if that's the case. Just want
> to make sure.
It is a read-only workload, as noted in the discussion of
Figure 9.5. For more realistic data structures and workloads,
see Chapter 10.
Thanx, Paul
prev parent reply other threads:[~2017-05-14 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 15:02 Question about performance figures in Section 9 Junchang Wang
2017-05-14 16:33 ` Paul E. McKenney [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=20170514163347.GO3956@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=junchangwang@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.