From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Werner Almesberger <werner@almesberger.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] set MS_NOATIME on FAT ?
Date: Wed, 16 Mar 2005 00:58:10 +0900 [thread overview]
Message-ID: <87zmx4x5nx.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20050315080407.T12802@almesberger.net> (Werner Almesberger's message of "Tue, 15 Mar 2005 08:04:07 -0300")
Werner Almesberger <werner@almesberger.net> writes:
> In the case of non-VFAT, there's also the issue that pretending to
> support atime causes atime to jump back and forth unpredictably,
> depending on when the inode is evicted from memory. (And the low
> adate resolution means that even VFAT will have a similar problem.)
Yes. We would need to add something to timespec_trunc() for it.
And unfortunately de->time too.
> But I guess if nobody complained in the last twelve or so years,
> we're in no hurry to fix that ;-)
Thanks. :)
> @@ -1059,6 +1131,8 @@ int fat_fill_super(struct super_block *s
> memset(sbi, 0, sizeof(struct msdos_sb_info));
>
> sb->s_flags |= MS_NODIRATIME;
> + if (!isvfat)
> + sb->s_flags |= MS_NOATIME;
> sb->s_magic = MSDOS_SUPER_MAGIC;
> sb->s_op = &fat_sops;
> sb->s_export_op = &fat_export_ops;
Looks good to me. But, I don't know whether actually DOS updates ->adate
or not. It would depend on it.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2005-03-15 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 2:20 [RFC] set MS_NOATIME on FAT ? Werner Almesberger
2005-03-15 3:56 ` OGAWA Hirofumi
2005-03-15 4:18 ` Werner Almesberger
2005-03-15 5:08 ` OGAWA Hirofumi
2005-03-15 11:04 ` Werner Almesberger
2005-03-15 15:58 ` OGAWA Hirofumi [this message]
2005-03-15 17:13 ` Werner Almesberger
2005-03-15 18:18 ` OGAWA Hirofumi
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=87zmx4x5nx.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=werner@almesberger.net \
/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