From: Joe Korty <joe.korty@ccur.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org, Ronny.Lampert@telecasystems.de,
ioe-lkml@rameria.de
Subject: Re: [BUG] NFS no longer updates file modification times appropriately
Date: Mon, 7 Jun 2004 12:39:20 -0400 [thread overview]
Message-ID: <20040607163920.GB22505@tsunami.ccur.com> (raw)
In-Reply-To: <1086625209.4597.0.camel@lade.trondhjem.org>
On Mon, Jun 07, 2004 at 12:20:11PM -0400, Trond Myklebust wrote:
> P? m? , 07/06/2004 klokka 12:13, skreiv Joe Korty:
> > >
> > > > In which case we
> > > > could defer a timestamp-on-write only when it is still in the same second
> > > > as the previous write, but don't defer when a new second rolls around
> > > > on the client. That would reduce timestamp updates to at most one per
> > > > second per inode per client, while preserving old NFS behavior.
> > >
> > > Exactly why should we go to all this trouble?
> >
> > For compatibility?
>
> With what? There has never been a standard other than the close-to-open.
Compatibility with existing behavior. It's called a de-facto standard.
next prev parent reply other threads:[~2004-06-07 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 20:28 Joe Korty
2004-06-03 21:11 ` Trond Myklebust
2004-06-04 3:25 ` Ingo Oeser
2004-06-06 19:17 ` Trond Myklebust
2004-06-04 13:23 ` Joe Korty
2004-06-04 23:08 ` Trond Myklebust
2004-06-04 23:24 ` Stephen Hemminger
2004-06-04 23:37 ` Trond Myklebust
2004-06-07 15:21 ` Joe Korty
2004-06-07 15:51 ` Trond Myklebust
2004-06-07 16:13 ` Joe Korty
2004-06-07 16:20 ` Trond Myklebust
2004-06-07 16:39 ` Joe Korty [this message]
2004-06-07 16:53 ` Trond Myklebust
2004-06-07 17:01 ` 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=20040607163920.GB22505@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=Ronny.Lampert@telecasystems.de \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®