On Fri, Mar 16, 2018 at 3:59 AM, Theodore Y. Ts'o wrote:
> On Thu, Mar 15, 2018 at 09:38:29PM +0100, Arnd Bergmann wrote:
>>
>> You could also have a resolution of less than a nanosecond. Note
>> that today, the file time stamps generated by the kernel are in
>> jiffies resolution, so at best one
On Thu, Mar 15, 2018 at 11:17:54PM -0700, Andiry Xu wrote:
> On Thu, Mar 15, 2018 at 7:59 PM, Theodore Y. Ts'o wrote:
> > On Thu, Mar 15, 2018 at 09:38:29PM +0100, Arnd Bergmann wrote:
> >>
> >> You could also have a resolution of less than a nanosecond. Note
> >> that today, the file time stamps
On Thu, Mar 15, 2018 at 7:59 PM, Theodore Y. Ts'o wrote:
> On Thu, Mar 15, 2018 at 09:38:29PM +0100, Arnd Bergmann wrote:
>>
>> You could also have a resolution of less than a nanosecond. Note
>> that today, the file time stamps generated by the kernel are in
>> jiffies resolution, so at best one
On Thu, Mar 15, 2018 at 09:38:29PM +0100, Arnd Bergmann wrote:
>
> You could also have a resolution of less than a nanosecond. Note
> that today, the file time stamps generated by the kernel are in
> jiffies resolution, so at best one millisecond. However, most modern
> file systems go with the 64
On Thu, Mar 15, 2018 at 6:51 PM, Andiry Xu wrote:
> On Thu, Mar 15, 2018 at 2:05 AM, Arnd Bergmann wrote:
>> On Thu, Mar 15, 2018 at 7:11 AM, Andiry Xu wrote:
>
> Superblock mtime is not a big problem as it is updated rarely. 64-bit
> seconds and 32-bit nanoseconds make the inode and log entry b
On Mar 15, 2018, at 11:51 AM, Andiry Xu wrote:
>
> On Thu, Mar 15, 2018 at 2:05 AM, Arnd Bergmann wrote:
>> On Thu, Mar 15, 2018 at 7:11 AM, Andiry Xu wrote:
>>> On Wed, Mar 14, 2018 at 9:54 PM, Darrick J. Wong
>>> wrote:
On Sat, Mar 10, 2018 at 10:17:44AM -0800, Andiry Xu wrote:
>>
On Thu, Mar 15, 2018 at 2:05 AM, Arnd Bergmann wrote:
> On Thu, Mar 15, 2018 at 7:11 AM, Andiry Xu wrote:
>> On Wed, Mar 14, 2018 at 9:54 PM, Darrick J. Wong
>> wrote:
>>> On Sat, Mar 10, 2018 at 10:17:44AM -0800, Andiry Xu wrote:
>
+ /* s_mtime and s_wtime should be together and their
On Thu, Mar 15, 2018 at 7:11 AM, Andiry Xu wrote:
> On Wed, Mar 14, 2018 at 9:54 PM, Darrick J. Wong
> wrote:
>> On Sat, Mar 10, 2018 at 10:17:44AM -0800, Andiry Xu wrote:
>>> + /* s_mtime and s_wtime should be together and their order should not
>>> be
>>> + * changed. we use an 8 byt
On Wed, Mar 14, 2018 at 9:54 PM, Darrick J. Wong
wrote:
> On Sat, Mar 10, 2018 at 10:17:44AM -0800, Andiry Xu wrote:
>> From: Andiry Xu
>>
>> This header file defines NOVA persistent and volatile superblock
>> data structures.
>>
>> It also defines NOVA block layout:
>>
>> Page 0: Superblock
>> P
On Sat, Mar 10, 2018 at 10:17:44AM -0800, Andiry Xu wrote:
> From: Andiry Xu
>
> This header file defines NOVA persistent and volatile superblock
> data structures.
>
> It also defines NOVA block layout:
>
> Page 0: Superblock
> Page 1: Reserved inodes
> Page 2 - 15: Reserved
> Page 16 - 31: In
From: Andiry Xu
This header file defines NOVA persistent and volatile superblock
data structures.
It also defines NOVA block layout:
Page 0: Superblock
Page 1: Reserved inodes
Page 2 - 15: Reserved
Page 16 - 31: Inode table pointers
Page 32 - 47: Journal address pointers
Page 48 - 63: Reserved
11 matches
Mail list logo