linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: dipankar@in.ibm.com
Cc: William Lee Irwin III <wli@holomorphy.com>,
	Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.69-mm1
Date: 06 May 2003 05:02:22 -0700	[thread overview]
Message-ID: <1052222542.983.27.camel@rth.ninka.net> (raw)
In-Reply-To: <20030506110907.GB9875@in.ibm.com>

On Tue, 2003-05-06 at 04:09, Dipankar Sarma wrote:
> That brings me to the point - with the fget-speedup patch, we should
> probably change ->file_lock back to an rwlock again. We now take this
> lock only when fd table is shared and under such situation the rwlock
> should help. Andrew, it that ok ?

rwlocks believe it or not tend not to be superior over spinlocks,
they actually promote cache line thrashing in the case they
are actually being effective (>1 parallel reader)

-- 
David S. Miller <davem@redhat.com>

  reply	other threads:[~2003-05-06 13:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05  6:16 2.5.69-mm1 Andrew Morton
2003-05-05 15:32 ` 2.5.69-mm1 Andrei Ivanov
2003-05-05 16:45   ` 2.5.69-mm1 Greg KH
2003-05-06  9:49     ` 2.5.69-mm1 Andrei Ivanov
2003-05-05 18:44   ` 2.5.69-mm1 Andrew Morton
2003-05-05 21:01 ` 2.5.69-mm1 William Lee Irwin III
2003-05-06 11:09   ` 2.5.69-mm1 Dipankar Sarma
2003-05-06 12:02     ` David S. Miller [this message]
2003-05-06 15:25       ` 2.5.69-mm1 Dipankar Sarma
2003-05-06 14:20         ` 2.5.69-mm1 David S. Miller
2003-05-06 15:47           ` 2.5.69-mm1 Dipankar Sarma
2003-05-05 21:02 ` 2.5.69-mm1 William Lee Irwin III
2003-05-06 14:33 ` 2.5.69-mm1 Steven Cole
2003-05-06 15:33   ` 2.5.69-mm1 Andrew Morton
2003-05-06 15:36     ` 2.5.69-mm1 Eric W. Biederman
2003-05-06 16:35       ` 2.5.69-mm1 Steven Cole

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=1052222542.983.27.camel@rth.ninka.net \
    --to=davem@redhat.com \
    --cc=akpm@digeo.com \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wli@holomorphy.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 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).