From: Edward Hibbert <EH@dataconnection.com>
To: "'Vivek Goyal'" <vivek.goyal@wipro.com>,
trond.myklebust@fys.uio.no, Ion Badulescu <ionut@badula.org>
Cc: viro@math.psu.edu, davem@redhat.com, ezk@cs.sunysb.edu,
indou.takao@jp.fujitsu.com, nfs@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: RE: [NFS] Disabling Symbolic Link Content Caching in NFS Client
Date: Tue, 3 Jun 2003 14:33:45 +0100 [thread overview]
Message-ID: <CFCD2C778CF1D611B5B400065B04D5C84A736F@KENTON> (raw)
-----Original Message-----
From: Vivek Goyal [mailto:vivek.goyal@wipro.com]
Sent: Tuesday, June 03, 2003 2:21 PM
To: trond.myklebust@fys.uio.no; Ion Badulescu
Cc: viro@math.psu.edu; davem@redhat.com; ezk@cs.sunysb.edu;
indou.takao@jp.fujitsu.com; nfs@lists.sourceforge.net;
linux-kernel@vger.kernel.org; Vivek Goyal
Subject: RE: [NFS] Disabling Symbolic Link Content Caching in NFS Client
<snip>
You are right. But our idea is to provide an option to disable/enable
caching based on the nature of intended application.
[EH] Hear hear :-).
Our application consists of a number of machines collaborating on a shared
database over NFS. We therefore require the ability to force data to be
sync'd from the client to the backend - and at the moment we do this by
disabling caching completely, via the noac option and acquiring and
releasing non-exclusive locks round io calls.
Any improvements in the granularity of control over NFS client-side caching
would be very valuable to us.
Regards,
Edward Hibbert
Internet Applications Group
Data Connection Ltd
Tel: +44 131 662 1212 Fax: +44 131 662 1345
Email: eh@dataconnection.com Web: http://www.dataconnection.com
next reply other threads:[~2003-06-03 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 13:33 Edward Hibbert [this message]
2003-06-03 14:46 ` Frank van Maarseveen
2003-06-03 16:08 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2003-06-03 13:20 Vivek Goyal
2003-06-03 16:05 ` Trond Myklebust
2003-05-28 11:09 Vivek Goyal
2003-06-02 20:37 ` [NFS] " Ion Badulescu
2003-06-02 21:48 ` Trond Myklebust
2003-06-02 21:56 ` Trond Myklebust
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=CFCD2C778CF1D611B5B400065B04D5C84A736F@KENTON \
--to=eh@dataconnection.com \
--cc=davem@redhat.com \
--cc=ezk@cs.sunysb.edu \
--cc=indou.takao@jp.fujitsu.com \
--cc=ionut@badula.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@math.psu.edu \
--cc=vivek.goyal@wipro.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
all inboxes | Powered by JetHome®