From: David Sariel <davidsa.openu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: atime
Date: Mon, 01 Aug 2011 08:53:33 +0300 [thread overview]
Message-ID: <4E363F5D.7060302@gmail.com> (raw)
In-Reply-To: <20110728.102536.53123850.ryusuke-sG5X7nlA6pw@public.gmane.org>
Hi
What was the purpose of reserving the inode for atime file (nilfs2_fs.h)
#define NILFS_ATIME_INO 7 /* Atime file (reserved) */
Correct me if I'm wrong, but it seems to me that updating atime on the disk
result in creating more chekpoints. So spesial file in predetermined
place can store
atime of all files in the system and spare the need of checkpointings of
many segments.
Also can you please share your thoughts about the atime implementation
on nilfs?
Thank you
David
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-08-01 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BLU152-W53BCFBB71148893681289CE350@phx.gbl>
[not found] ` <BLU152-W1990E7DAA23E5566FC3925CE350@phx.gbl>
[not found] ` <BLU152-W1990E7DAA23E5566FC3925CE350-MsuGFMq8XAE@public.gmane.org>
2011-07-27 21:19 ` How to restore snaspshot in nilfs? ffffd sssd
[not found] ` <BLU152-W567E135957B79607CC415ECE350-MsuGFMq8XAE@public.gmane.org>
2011-07-28 1:25 ` Ryusuke Konishi
[not found] ` <20110728.102536.53123850.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-08-01 5:53 ` David Sariel [this message]
[not found] ` <4E363F5D.7060302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-08-02 3:24 ` atime Ryusuke Konishi
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=4E363F5D.7060302@gmail.com \
--to=davidsa.openu-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=davidsa-BMswWb+h+80+JF/nGntIXQ@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.