Searched hist:"5 a64efa1" (Results 1 – 4 of 4) sorted by relevance
| /dragonfly/sys/vfs/hammer/ |
| H A D | hammer_transaction.c | 5a64efa1 Sun Jun 21 02:29:57 GMT 2009 Matthew Dillon <dillon@apollo.backplane.com> HAMMER VFS - Implement inode number matching against the directory hash
Change hammer_create_inode() and hammer_alloc_objid() to take the upper
10 bits of the filename hash and attempt to use them as the lower 10 bits
of the inode number.
hammer_alloc_objid() now utilizes a small two-level 1024-bit bitmap to
assign the low 10 bits of the inode number, on a per-directory basis.
If a collision occurs a nearby value is used instead.
The idea is for inode numbers to have approximately the same linearity
as the directory read scan order, so programs such as cpio, tar, cpdup,
find, and ls which do recursive scans of the directory tree get much
better locality of reference for stat() and other related system calls.
Based-on: Numerous discussions with people, esp corecode.
|
| H A D | hammer_inode.c | 5a64efa1 Sun Jun 21 02:29:57 GMT 2009 Matthew Dillon <dillon@apollo.backplane.com> HAMMER VFS - Implement inode number matching against the directory hash
Change hammer_create_inode() and hammer_alloc_objid() to take the upper
10 bits of the filename hash and attempt to use them as the lower 10 bits
of the inode number.
hammer_alloc_objid() now utilizes a small two-level 1024-bit bitmap to
assign the low 10 bits of the inode number, on a per-directory basis.
If a collision occurs a nearby value is used instead.
The idea is for inode numbers to have approximately the same linearity
as the directory read scan order, so programs such as cpio, tar, cpdup,
find, and ls which do recursive scans of the directory tree get much
better locality of reference for stat() and other related system calls.
Based-on: Numerous discussions with people, esp corecode.
|
| H A D | hammer_vnops.c | 5a64efa1 Sun Jun 21 02:29:57 GMT 2009 Matthew Dillon <dillon@apollo.backplane.com> HAMMER VFS - Implement inode number matching against the directory hash
Change hammer_create_inode() and hammer_alloc_objid() to take the upper
10 bits of the filename hash and attempt to use them as the lower 10 bits
of the inode number.
hammer_alloc_objid() now utilizes a small two-level 1024-bit bitmap to
assign the low 10 bits of the inode number, on a per-directory basis.
If a collision occurs a nearby value is used instead.
The idea is for inode numbers to have approximately the same linearity
as the directory read scan order, so programs such as cpio, tar, cpdup,
find, and ls which do recursive scans of the directory tree get much
better locality of reference for stat() and other related system calls.
Based-on: Numerous discussions with people, esp corecode.
|
| H A D | hammer.h | 5a64efa1 Sun Jun 21 02:29:57 GMT 2009 Matthew Dillon <dillon@apollo.backplane.com> HAMMER VFS - Implement inode number matching against the directory hash
Change hammer_create_inode() and hammer_alloc_objid() to take the upper
10 bits of the filename hash and attempt to use them as the lower 10 bits
of the inode number.
hammer_alloc_objid() now utilizes a small two-level 1024-bit bitmap to
assign the low 10 bits of the inode number, on a per-directory basis.
If a collision occurs a nearby value is used instead.
The idea is for inode numbers to have approximately the same linearity
as the directory read scan order, so programs such as cpio, tar, cpdup,
find, and ls which do recursive scans of the directory tree get much
better locality of reference for stat() and other related system calls.
Based-on: Numerous discussions with people, esp corecode.
|