All of lore.kernel.org
 help / color / mirror / Atom feed
From: mingming cao <cmm@us.ibm.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Manfred Spraul <manfred@colorfullife.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]IPC locks breaking down with RCU
Date: Mon, 21 Oct 2002 13:34:01 -0700	[thread overview]
Message-ID: <3DB464B9.7B44EB48@us.ibm.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210212056390.17270-100000@localhost.localdomain

Hugh Dickins wrote:
> 
> In the original design, Mingming nicely split up the locks (greatly
> reducing contention), but had them in an array (causing lots of bounce,
> I believe): 
I am not an expert of cacheline bouncing, so please point me if I miss
something.  I wonder if we could reduce the bounce even with current
design (the spinlock is in the data it protects).  We have to go through
that array anyway to get access to the data (and the spinlock).

> I'm resisting a return to that design.
OK, I will back to original design.

  reply	other threads:[~2002-10-21 20:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 19:23 [PATCH]IPC locks breaking down with RCU Manfred Spraul
2002-10-21 20:10 ` Hugh Dickins
2002-10-21 20:34   ` mingming cao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-18  0:14 mingming cao
2002-10-20 13:14 ` Hugh Dickins
2002-10-20 17:27   ` Hugh Dickins
2002-10-21 18:11     ` mingming cao
2002-10-21 19:00       ` Hugh Dickins
2002-10-21 19:18       ` Dipankar Sarma
2002-10-21 19:36         ` Hugh Dickins
2002-10-21 19:41         ` mingming cao
2002-10-21 20:14           ` Dipankar Sarma
2002-10-21 18:07   ` mingming cao

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=3DB464B9.7B44EB48@us.ibm.com \
    --to=cmm@us.ibm.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.