From: viro@parcelfarce.linux.theplanet.co.uk
To: Dipankar Sarma <dipankar@in.ibm.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
John M Flinchbaugh <glynis@butterfly.hjsoft.com>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
Maneesh Soni <maneesh@in.ibm.com>
Subject: Re: 2.5.70-bk16: nfs crash
Date: Thu, 12 Jun 2003 17:30:45 +0100 [thread overview]
Message-ID: <20030612163045.GK6754@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030612155345.GB1438@in.ibm.com>
On Thu, Jun 12, 2003 at 09:23:45PM +0530, Dipankar Sarma wrote:
> Lockfree d_lookup() gives us significant benefits in larger
> SMP machines.
I wonder if they outweight debugging time wasted after any change...
Note that for vfsmounts proposed RCU patch had been utterly useless -
practically all improvements had been from separate lock for vfsmounts
(see akpm tree).
next prev parent reply other threads:[~2003-06-12 16:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 12:56 2.5.70-bk16: nfs crash John M Flinchbaugh
2003-06-12 13:52 ` Dipankar Sarma
2003-06-12 15:33 ` Dipankar Sarma
2003-06-12 15:35 ` Trond Myklebust
2003-06-12 15:53 ` Dipankar Sarma
2003-06-12 16:26 ` Trond Myklebust
2003-06-12 16:49 ` Linus Torvalds
2003-06-12 16:55 ` Linus Torvalds
2003-06-12 19:53 ` Dipankar Sarma
2003-06-13 5:24 ` Trond Myklebust
2003-06-13 5:50 ` Dipankar Sarma
2003-06-13 6:13 ` Trond Myklebust
2003-06-13 6:54 ` Dipankar Sarma
2003-06-13 6:06 ` Dipankar Sarma
2003-06-12 16:30 ` viro [this message]
2003-06-12 16:55 ` Dipankar Sarma
2003-06-12 15:49 ` Linus Torvalds
2003-06-12 16:05 ` Dipankar Sarma
2003-06-12 16:18 ` Linus Torvalds
2003-06-12 16:35 ` Dipankar Sarma
2003-06-12 16:47 ` Linus Torvalds
2003-06-13 12:48 ` Maneesh Soni
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=20030612163045.GK6754@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=dipankar@in.ibm.com \
--cc=glynis@butterfly.hjsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=torvalds@transmeta.com \
--cc=trond.myklebust@fys.uio.no \
/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