LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: "Paul E. McKenney" <email@example.com> To: Joel Fernandes <firstname.lastname@example.org> Cc: email@example.com, firstname.lastname@example.org, Josh Triplett <email@example.com>, Steven Rostedt <firstname.lastname@example.org>, Mathieu Desnoyers <email@example.com>, Lai Jiangshan <firstname.lastname@example.org>, Andrea Parri <email@example.com>, Jonathan Corbet <firstname.lastname@example.org>, email@example.com Subject: Re: [PATCH] doc/rcu: Correct field_count field naming in examples Date: Tue, 14 May 2019 15:13:32 -0700 [thread overview] Message-ID: <20190514221332.GC4184@linux.ibm.com> (raw) In-Reply-To: <20190513034305.GB96252@google.com> On Sun, May 12, 2019 at 11:43:05PM -0400, Joel Fernandes wrote: > On Wed, May 08, 2019 at 11:16:38AM -0700, Paul E. McKenney wrote: > [snip] > > > The other example could be dentry look up which uses seqlocks for the > > > RCU-walk case? But that could be too complex. This is also something I first > > > learnt from the paper and then the excellent path-lookup.rst document in > > > kernel sources. > > > > This is a great example, but it would need serious simplification for > > use in the Documentation/RCU directory. Note that dcache uses it to > > gain very limited and targeted consistency -- only a few types of updates > > acquire the write-side of that seqlock. > > > > Might be quite worthwhile to have a simplified example, though! > > Perhaps a trivial hash table where write-side sequence lock is acquired > > only when moving an element from one chain to another? > > Here you meant "moving from one chain to another" in the case of > hashtable-resizing right? I could not think of another reason why an element > is moved between 2 hash chains. Either that or in terms of atomic rekeying of a specific element in that table, thus potentially requiring an atomic move of only that specific element to another hash chain. > I just finished reading the main parts of Josh's relativistic hashtable paper >  and it is very cool indeed. The whole wait-for-readers application for > hashtable expansion is so well thought. I am planning to go over more papers > and code and can certainly update this example with a read-mostly hashtable > example as well as you are suggesting. :-) > >  https://www.usenix.org/legacy/event/atc11/tech/final_files/Triplett.pdf Sounds very good! Thanx, Paul
next prev parent reply other threads:[~2019-05-14 22:13 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-05 2:03 [PATCH] doc/rcu: Correct field_count field naming in examples Joel Fernandes (Google) 2019-05-07 0:04 ` Paul E. McKenney 2019-05-08 16:26 ` Joel Fernandes 2019-05-08 18:16 ` Paul E. McKenney 2019-05-11 22:11 ` Andrea Parri 2019-05-12 0:41 ` Paul E. McKenney 2019-05-12 1:09 ` Andrea Parri 2019-05-13 3:43 ` Joel Fernandes 2019-05-14 22:13 ` Paul E. McKenney [this message] 2019-05-25 10:07 ` Joel Fernandes
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=20190514221332.GC4184@linux.ibm.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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: linkBe 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 NNTP newsgroup(s).