From: "Paul E. McKenney" <paulmck@kernel.org>
To: Alan Huang <mmpgouride@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] defer/whichtochoose: Make paragraph consistent with table
Date: Mon, 1 May 2023 09:20:26 -0700 [thread overview]
Message-ID: <400ede1f-d3c9-4146-9e15-9a88c892dacf@paulmck-laptop> (raw)
In-Reply-To: <20230501151112.24312-1-mmpgouride@gmail.com>
On Mon, May 01, 2023 at 03:11:12PM +0000, Alan Huang wrote:
> The second row of table 9.7 has been changed since 82c89c8.
> So make the paragraph consistent with the table.
>
> Signed-off-by: Alan Huang <mmpgouride@gmail.com>
Good eyes, queued and pushed, thank you!
Thanx, Paul
> ---
> defer/whichtochoose.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/defer/whichtochoose.tex b/defer/whichtochoose.tex
> index 10cb760e..af5a09c3 100644
> --- a/defer/whichtochoose.tex
> +++ b/defer/whichtochoose.tex
> @@ -85,7 +85,7 @@ The ``Readers'' row summarizes the results presented in
> which shows that all but \IXalt{reference counting}{reference count}
> enjoy reasonably fast and scalable readers.
>
> -The ``Number of Protected Objects'' row evaluates each technique's need
> +The ``Memory Overhead'' row evaluates each technique's need
> for external storage with which to record reader protection.
> RCU relies on quiescent states, and thus needs no storage to represent
> readers, whether within or outside of the object.
> --
> 2.34.1
>
prev parent reply other threads:[~2023-05-01 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 15:11 [PATCH] defer/whichtochoose: Make paragraph consistent with table Alan Huang
2023-05-01 16:20 ` 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=400ede1f-d3c9-4146-9e15-9a88c892dacf@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=mmpgouride@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 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).