From: Elad Lahav <e2lahav@gmail.com>
To: perfbook@vger.kernel.org
Subject: [PATCH-perfbook] count: The fast path is for the write side
Date: Fri, 12 Aug 2022 14:38:06 -0400 [thread overview]
Message-ID: <CAJbg=FV_ngVf2dKkaTMD0QM1713ppDBj-yfQJTOuqmnUUyOncw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
Sent as an attachment because I'm behind a corporate firewall and can
only use Gmail's ^$*&^@# web interface. If that's not acceptable I'll
find another method to send a Real Text Email, just like mother nature
intended it to be.
--Elad
[-- Attachment #2: 0001-count-The-fast-path-is-for-the-write-side-not-the-re.patch --]
[-- Type: text/x-patch, Size: 1025 bytes --]
From 153cd4261fe58ed7f26bb0b1232eae2de43070ad Mon Sep 17 00:00:00 2001
From: Elad Lahav <elahav@qnx.com>
Date: Fri, 12 Aug 2022 13:04:08 -0400
Subject: [PATCH] count: The fast path is for the write side, not the read
side.
Signed-off-by: Elad Lahav <e2lahav@gmail.com>
---
count/count.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/count/count.tex b/count/count.tex
index 7e74d58f..523789e2 100644
--- a/count/count.tex
+++ b/count/count.tex
@@ -2262,7 +2262,7 @@ be run all the way to either of its limits, but it does so at the
expense of adding atomic operations to the fastpaths, which slow down
the fastpaths significantly on some systems.
Although some workloads might tolerate this slowdown, it is worthwhile
-looking for algorithms with better read-side performance.
+looking for algorithms with better write-side performance.
One such algorithm uses a signal handler to steal counts from other
threads.
Because signal handlers run in the context of the signaled thread,
--
2.25.1
next reply other threads:[~2022-08-12 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 18:38 Elad Lahav [this message]
2022-08-12 21:15 ` [PATCH-perfbook] count: The fast path is for the write side Paul E. McKenney
2022-08-13 2:12 ` Akira Yokosawa
2022-08-13 2:19 ` 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='CAJbg=FV_ngVf2dKkaTMD0QM1713ppDBj-yfQJTOuqmnUUyOncw@mail.gmail.com' \
--to=e2lahav@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).