From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: nfs@lists.sourceforge.net, Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Eliminating the BKL from the NFS and RPC clients
Date: Fri, 19 Jan 2007 01:23:49 +0000 [thread overview]
Message-ID: <20070119012349.GA25491@infradead.org> (raw)
In-Reply-To: <45B00585.10001@oracle.com>
056-nfs-smp-change_attribute.diff:
are the barriers really enough? Don't you need at least a lock on
the writer side?
057-noattr_flag.diff:
I don't really like this approach. Can we make touch_atime
and file_update_time go ghrough ->setattr instead? Having all
attribute updates going through setattr would fix up quite a
lot of mess we have, also in other filesystems like xfs.
In either case this really needs to go through -fsdevel
059-nfs-serialize-change_attr.diff:
Please don't spread all these CONFIG_NFS_V4 around, they don't really
seem to help much.
-------------------------------------------------------------------------
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
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-01-19 1:23 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 [this message]
2007-01-19 5:36 ` Trond Myklebust
2007-01-20 9:33 ` Christoph Hellwig
2007-01-24 20:28 ` Chuck Lever
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=20070119012349.GA25491@infradead.org \
--to=hch@infradead.org \
--cc=chuck.lever@oracle.com \
--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