mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Two other ways to do latched seqcounts
Date: 13 Apr 2015 05:26:05 -0400	[thread overview]
Message-ID: <20150413092605.2469.qmail@ns.horizon.com> (raw)
In-Reply-To: <20150413073510.GC5029@twins.programming.kicks-ass.net>

> I'm assuming you're writing to me because of the latched rb-tree;
> because that's the most recent related thing I posted ;-)

Basically yes, although it was the documentation you added to the
latched seqlock code in particular.

I haven't checked the users of your rb-tree code to see how large and
frequently read the trees are, but if a read is expensive, then avoiding
retries by incrementing the seqlock twice per update starts to become
interesting.

       reply	other threads:[~2015-04-13  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150413073510.GC5029@twins.programming.kicks-ass.net>
2015-04-13  9:26 ` George Spelvin [this message]
2015-04-13 10:38   ` Peter Zijlstra
2015-04-12 19:36 George Spelvin

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=20150413092605.2469.qmail@ns.horizon.com \
    --to=linux@horizon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®