Linux filesystem development
 help / color / mirror / Atom feed
From: simo <idra@samba.org>
To: Steve French <smfrench@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-cifs-client@lists.samba.org,
	Jeff Layton <jlayton@redhat.com>,
	Guenter Kukkukk <linux@kukkukk.com>
Subject: Re: Re: set last write time = fsync ?
Date: Sat, 15 Mar 2008 10:51:59 -0400	[thread overview]
Message-ID: <1205592719.9351.30.camel@localhost.localdomain> (raw)
In-Reply-To: <524f69650803140916w1dde16a9ja9dc4e052edd77e5@mail.gmail.com>


On Fri, 2008-03-14 at 11:16 -0500, Steve French wrote:
> I don't worry about flushing atime (anyone crazy enough to do that
> would pay a huge performance penalty).
> Access is usually checked on open right ... so once a file is open
> even if the file becomes read-only, the writes, even cached writes
> continue.

Is this true even in the case you loose the connection with the server
and need to re-establish it ?

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer <simo@samba.org>
Senior Software Engineer at Red Hat Inc. <ssorce@redhat.com>

  parent reply	other threads:[~2008-03-15 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <524f69650803122054t7b0f8285kd564271f8340378e@mail.gmail.com>
     [not found] ` <20080313071046.1a9350a9@tleilax.poochiereds.net>
2008-03-14  2:32   ` set last write time = fsync ? Steve French
2008-03-14 10:40     ` Jeff Layton
2008-03-14 16:16       ` Steve French
2008-03-14 16:55         ` Jeff Layton
2008-03-14 19:19           ` Steve French
2008-03-14 20:35             ` Jeff Layton
2008-03-14 21:38               ` Steve French
2008-03-14 23:19                 ` Jeff Layton
2008-03-15 14:51         ` simo [this message]
2008-03-15 15:35           ` [linux-cifs-client] " Steve French

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=1205592719.9351.30.camel@localhost.localdomain \
    --to=idra@samba.org \
    --cc=jlayton@redhat.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux@kukkukk.com \
    --cc=smfrench@gmail.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