From: Boaz Harrosh <openosd@gmail.com>
To: Dan Luedtke <mail@danrl.de>
Cc: 김재극 <jaegeuk.kim@samsung.com>,
viro@zeniv.linux.org.uk, "'Theodore Ts'o'" <tytso@mit.edu>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
chur.lee@samsung.com, cm224.lee@samsung.com,
jooyoung.hwang@samsung.com
Subject: Re: [PATCH 02/16] f2fs: add on-disk layout
Date: Fri, 05 Oct 2012 14:09:36 -0700 [thread overview]
Message-ID: <506F4C90.1010003@gmail.com> (raw)
In-Reply-To: <1349459677.22620.4.camel@tunafish>
On 10/05/2012 10:54 AM, Dan Luedtke wrote:
> On Fri, 2012-10-05 at 20:56 +0900, 김재극 wrote:
>> + __le32 i_atime; /* Access time */
>> + __le32 i_ctime; /* inode Change time */
>> + __le32 i_mtime; /* Modification time */
>> + __le32 i_btime; /* file creation time*/
>
> It's probably to late, but have you considered using 64 bit timestamps?
> In LanyFS we use 64 bit and I'm very interested in reasoning for 32 bit
> timestamps.
>
Yes and please don't make them millisecond resolution. This is a real headache.
>From the like of make to NFS to reboot/corruption recovery... the list is endless
Please make it nanoseconds resolution.
> Regards
>
> Dan
>
Thanks
Boaz
next prev parent reply other threads:[~2012-10-05 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 11:56 [PATCH 02/16] f2fs: add on-disk layout 김재극
2012-10-05 17:46 ` Martin Steigerwald
2012-10-06 18:25 ` Jaegeuk Kim
2012-10-05 17:54 ` Dan Luedtke
2012-10-05 21:09 ` Boaz Harrosh [this message]
2012-10-06 18:19 ` Jaegeuk Kim
2012-10-06 22:21 ` David Sterba
2012-10-09 5:27 ` Chul Lee
2012-10-07 6:42 ` Stefan Hajnoczi
2012-10-10 5:52 ` Jaegeuk Kim
2012-10-12 21:05 ` Arnd Bergmann
2012-10-13 11:39 ` Jaegeuk Kim
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=506F4C90.1010003@gmail.com \
--to=openosd@gmail.com \
--cc=chur.lee@samsung.com \
--cc=cm224.lee@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaegeuk.kim@samsung.com \
--cc=jooyoung.hwang@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@danrl.de \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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.