Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 0/6] Simplify hash_resize.c
Date: Tue, 15 Jan 2019 16:07:52 -0800	[thread overview]
Message-ID: <20190116000751.GE1215@linux.ibm.com> (raw)
In-Reply-To: <8dcb7b16-d7c2-b336-de97-469fd944f72c@gmail.com>

On Wed, Jan 16, 2019 at 07:29:53AM +0900, Akira Yokosawa wrote:
> On 2019/01/13 18:10:24 -0800, Paul E. McKenney wrote:
> > On Mon, Jan 14, 2019 at 08:28:27AM +0900, Akira Yokosawa wrote:
> >> >From 7b69a9b37ba9a73a50aad5cbb097235ddfe75870 Mon Sep 17 00:00:00 2001
> >> From: Akira Yokosawa <akiyks@gmail.com>
> >> Date: Mon, 14 Jan 2019 07:25:14 +0900
> >> Subject: [PATCH 0/6] Simplify hash_resize.c
> >>
> >> Hi Paul,
> >>
> >> This patch set updates hash_resize.c, which you suggested for me to
> >> take over, and the related text.
> >>
> >> I added a couple of Quick Quizzes as well, and in one of them,
> >> I included your version of hash_resize.c.
> >>
> >> Patch #1 updates hash_resize.c in the way I suggested. Note that
> >> in this update, "#ifndef FCV_SNIPPET" blocks are used to hide
> >> code for debugging (hash value checks) in code snippets.
> >> This code can actually be compiled with "-DFCV_SNIPPET" to see
> >> the performance without hash value checks.
> >>
> >> Patch #2 adds a couple of Quick Quizzes. Your version of hash_resize.c
> >> is added as hash_resize_s.c.
> >>
> >> Patch #3 removes unnecessary folding in a code snippet.
> >>
> >> Patch #4 adjusts a few sentence to the simpler approach.
> >>
> >> Patch #5 adds another Quick Quiz.
> >>
> >> Patch #6 adds an "#error" directive for the lack of rcu_barrier().
> >>
> >> All of the updates in text would need your native eyes to be polished.
> > 
> > Nice!  Queued and pushed, thank you!  I will review and send any
> > needed update by end of tomorrow, Pacific Time.
> > 
> > Just FYI, this also pushed out a couple of commits starting my rework
> > of Section 9.5.1.
> > 
> >>         Thanks, Akira
> >>
> >> PS:
> >>
> >> I couldn't make out your concern of "if we ever want to iterate over
> >> the hash table". Can you elaborate it?
> > 
> > Consider a hash_iterate() function that takes a pointer to a function.
> > Then hash_iterate() would invoke this function on each element currently
> > in the hash table, for a relatively relaxed definition of "currently".
> > With your hash table, a naive implementation might iterate over some
> > data items twice due to their being in both the old and the new tables.
> 
> If we stick to the old table, which is kept updated during resizing,
> there shouldn't be any duplication of items.
> 
> What am I missing?

Fair point.  Please accept my apologies for my confusion.  I think that
the right person is now maintaining hash_resize.c.  ;-)

							Thanx, Paul

>         Thanks, Akira
> 
> > 
> > But this is not hard to fix, for example, by creating some sort of list
> > of elements and the eliminating duplicates, then invoking the specified
> > function on each of them.  Of course, this entire process would need to
> > be carried out within an RCU read-side critical section.
> > 
> > This assumes that iteration over the entire hash table is rare, which
> > I would certainly expect it to be, given how expensive it is.
> > 
> > Plus, we currently don't support iteration, so it isn't currently a
> > problem anyway.  ;-)
> > 
> > 							Thanx, Paul
> > 
> >> --
> >> Akira Yokosawa (6):
> >>   datastruct/hash: Simplify hash_resize.c
> >>   datastruct/hash: Add a couple of Quick Quizzes regarding hash_resize.c
> >>   datastruct/hash: Fix unnecessary folding in code snippet
> >>   datastruct/hash: Adjust context to updated code in hash_resize.c
> >>   datastruct/hash: Add Quick Quiz on READ_ONCE/WRITE_ONCE in
> >>     hash_resize.c
> >>   datastruct/hash: Display error msg if rcu_barrier() is not available
> >>
> >>  CodeSamples/datastruct/hash/Makefile        |   5 +-
> >>  CodeSamples/datastruct/hash/hash_resize.c   |  62 +++--
> >>  CodeSamples/datastruct/hash/hash_resize_s.c | 365 ++++++++++++++++++++++++++++
> >>  CodeSamples/datastruct/hash/hashtorture.h   |  11 +-
> >>  datastruct/datastruct.tex                   | 146 +++++++----
> >>  5 files changed, 513 insertions(+), 76 deletions(-)
> >>  create mode 100644 CodeSamples/datastruct/hash/hash_resize_s.c
> >>
> >> -- 
> >> 2.7.4
> >>
> > 
> 


      reply	other threads:[~2019-01-16  0:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-13 23:28 [PATCH 0/6] Simplify hash_resize.c Akira Yokosawa
2019-01-13 23:31 ` [PATCH 1/6] datastruct/hash: " Akira Yokosawa
2019-01-14 10:31   ` Junchang Wang
2019-01-14 13:22     ` Akira Yokosawa
2019-01-14 14:16       ` Junchang Wang
2019-01-13 23:32 ` [PATCH 2/6] datastruct/hash: Add a couple of Quick Quizzes regarding hash_resize.c Akira Yokosawa
2019-01-13 23:33 ` [PATCH 3/6] datastruct/hash: Fix unnecessary folding in code snippet Akira Yokosawa
2019-01-13 23:35 ` [PATCH 4/6] datastruct/hash: Adjust context to updated code in hash_resize.c Akira Yokosawa
2019-01-13 23:36 ` [PATCH 5/6] datastruct/hash: Add Quick Quiz on READ_ONCE/WRITE_ONCE " Akira Yokosawa
2019-01-13 23:38 ` [PATCH 6/6] datastruct/hash: Display error msg if rcu_barrier() is not available Akira Yokosawa
2019-01-14  2:10 ` [PATCH 0/6] Simplify hash_resize.c Paul E. McKenney
2019-01-15  1:33   ` Paul E. McKenney
2019-01-15 15:32     ` Akira Yokosawa
2019-01-15 17:43       ` Paul E. McKenney
2019-01-15 22:15         ` Akira Yokosawa
2019-01-16  0:06           ` Paul E. McKenney
2019-01-15 22:29   ` Akira Yokosawa
2019-01-16  0:07     ` 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=20190116000751.GE1215@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=akiyks@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