public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [Fwd: [PATCH 2/7] lock_list: a fine grain locked double linked list]
Date: Mon, 29 Jan 2007 10:25:31 +0000	[thread overview]
Message-ID: <20070129102531.GA26884@infradead.org> (raw)
In-Reply-To: <1170066040.6189.128.camel@twins>

On Mon, Jan 29, 2007 at 11:20:40AM +0100, Peter Zijlstra wrote:
> klist is quite different in that it locks the whole list. The proposed
> data structure locks each edge, that is it will allow concurrent
> deletion of elements as long as they don't share neighbours.

Yes, that's one of the reasons why I dislike klist even more ;-) 


      reply	other threads:[~2007-01-29 10:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-28 15:53 [Fwd: [PATCH 2/7] lock_list: a fine grain locked double linked list] Peter Zijlstra
2007-01-28 17:20 ` Christoph Hellwig
2007-01-29 10:20   ` Peter Zijlstra
2007-01-29 10:25     ` Christoph Hellwig [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=20070129102531.GA26884@infradead.org \
    --to=hch@infradead.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@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