hammer: fix terminology of "large block"
authorTomohiro Kusumi <kusumi.tomohiro@gmail.com>
Sat, 31 Jan 2015 21:35:10 +0000 (06:35 +0900)
committerAntonio Huete Jimenez <tuxillo@quantumachine.net>
Sat, 7 Feb 2015 11:08:49 +0000 (12:08 +0100)
commite04ee2deffe511013c324e593719d66829589284
tree1ca623db4f4e54a2602ec4d68f19233543bda721
parent0b4d026e9789b12bc4fb18a0650e71d5573c39be
hammer: fix terminology of "large block"

This cleanup patch changes terminology "large block" to "big block".

- Both "large block" and "big block" are widely used in hammer source from
kernel to userspace, however these two refer to the same data structure which
is a 8MB sized chunk within low level blockmapped storage layer.

- The original design document https://www.dragonflybsd.org/hammer/hammer.pdf
uses big block for this data structure. Having two expressions in its
implementation is confusing and makes grep difficult.

Closes: #2782
16 files changed:
sbin/hammer/blockmap.c
sbin/hammer/cmd_blockmap.c
sbin/hammer/cmd_info.c
sbin/hammer/cmd_reblock.c
sbin/hammer/cmd_show.c
sbin/hammer/ondisk.c
sbin/newfs_hammer/newfs_hammer.c
sys/vfs/hammer/hammer_blockmap.c
sys/vfs/hammer/hammer_dedup.c
sys/vfs/hammer/hammer_disk.h
sys/vfs/hammer/hammer_ioctl.c
sys/vfs/hammer/hammer_ondisk.c
sys/vfs/hammer/hammer_reblock.c
sys/vfs/hammer/hammer_undo.c
sys/vfs/hammer/hammer_vfsops.c
sys/vfs/hammer/hammer_volume.c