From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Christoph Hellwig <hch@infradead.org>, nfs@lists.sourceforge.net
Subject: Re: Eliminating the BKL from the NFS and RPC clients
Date: Wed, 24 Jan 2007 15:28:05 -0500 [thread overview]
Message-ID: <45B7C155.3020900@oracle.com> (raw)
In-Reply-To: <1169184980.6158.19.camel@lade.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
Trond Myklebust wrote:
> On Fri, 2007-01-19 at 01:23 +0000, Christoph Hellwig wrote:
>> 056-nfs-smp-change_attribute.diff:
>> are the barriers really enough? Don't you need at least a lock on
>> the writer side?
>
> The change attribute should always be updated under the inode->lock
> anyway. I'm not really sure we need these.
What about nfs_end_data_update ?
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 276 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture Linux Projects Group
email;internet:chuck dot lever at nospam oracle dot com
title:Principle Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-01-24 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 23:40 Eliminating the BKL from the NFS and RPC clients Chuck Lever
2007-01-19 1:23 ` Christoph Hellwig
2007-01-19 5:36 ` Trond Myklebust
2007-01-20 9:33 ` Christoph Hellwig
2007-01-24 20:28 ` Chuck Lever [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=45B7C155.3020900@oracle.com \
--to=chuck.lever@oracle.com \
--cc=hch@infradead.org \
--cc=nfs@lists.sourceforge.net \
--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