Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1 |
|
#
3cd578ed |
| 21-Sep-2017 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Add uuid.c
Add a simple wrapper over uuid functions for better portability, similar to sys/vfs/hammer/hammer_crc.h (which helped implement version 7 CRC).
No functional changes.
|
Revision tags: v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1 |
|
#
f3f3fa72 |
| 11-Aug-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/newfs_hammer: Link against sbin/hammer/misc.o
Make /sbin/newfs_hammer link to sbin/hammer/misc.o, and use sizetostr() via sbin/hammer/misc.o instead of having its own one, by moving sbin/hammer
sbin/newfs_hammer: Link against sbin/hammer/misc.o
Make /sbin/newfs_hammer link to sbin/hammer/misc.o, and use sizetostr() via sbin/hammer/misc.o instead of having its own one, by moving sbin/hammer/misc.c prototypes to hammer_util.h.
It's okay to do this because /sbin/newfs_hammer fully depends on data structures of sbin/hammer/*. It's just better to make use of sbin/hammer/misc.o except that the binary becomes a bit larger.
The difference between hammer.h and hammer_util.h is that hammer.h is specific to /sbin/hammer. hammer_util.h seems to have been made for more general stuff that could be used by other programs like /sbin/hammer (but not outbox programs as the header isn't exposed to outside the dfly source).
show more ...
|
Revision tags: v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc |
|
#
45032ebd |
| 17-Sep-2015 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Remove -DALIST_NO_DEBUG
-DALIST_NO_DEBUG is no longer necessary.
sys/kern/subr_alist.c was only used in the early stage of hammer devel, and no longer used.
# grep ALIST_NO_DEBUG .
sbin/hammer: Remove -DALIST_NO_DEBUG
-DALIST_NO_DEBUG is no longer necessary.
sys/kern/subr_alist.c was only used in the early stage of hammer devel, and no longer used.
# grep ALIST_NO_DEBUG . -rI ./sbin/newfs_hammer/Makefile:CFLAGS+= -I${.CURDIR}/../../sys -I${.CURDIR}/../hammer -DALIST_NO_DEBUG ./sbin/hammer/Makefile:CFLAGS+= -I${.CURDIR}/../../sys -DALIST_NO_DEBUG ./sys/kern/subr_alist.c:#ifndef ALIST_NO_DEBUG
show more ...
|
Revision tags: v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc |
|
#
992ed92c |
| 28-May-2015 |
Matthew Dillon <dillon@apollo.backplane.com> |
hammer - Fix build for crc changes
* hammer uses the old crc code but needs the crc_tab from the new code.
|
Revision tags: v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
#
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather than continuing to create new binutils branches for each new version.
|
Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1, v2.0.1 |
|
#
f03c9cf4 |
| 23-Feb-2008 |
Matthew Dillon <dillon@dragonflybsd.org> |
HAMMER 30/many: blockmap work.
* Give the hammer utility the ability to decode blockmaps. 'hammer show' can dump the B-Tree again.
* Fix a couple of bugs in newfs_hammer's initialization of the
HAMMER 30/many: blockmap work.
* Give the hammer utility the ability to decode blockmaps. 'hammer show' can dump the B-Tree again.
* Fix a couple of bugs in newfs_hammer's initialization of the freemap.
* Implement reallocation within the freemap (poor-man's version).
* Implement reallocation within a zone (poor-man's version). Add a sysctl vfs.hammer.zone_limit to artificially reduce the size of the zone to force it to cycle.
show more ...
|
#
47197d71 |
| 08-Feb-2008 |
Matthew Dillon <dillon@dragonflybsd.org> |
HAMMER 27/many: Major surgery - change allocation model
After getting stuck on the recovery code and highly unoptimal write performance issues, remove the super-cluster/cluster and radix tree bitmap
HAMMER 27/many: Major surgery - change allocation model
After getting stuck on the recovery code and highly unoptimal write performance issues, remove the super-cluster/cluster and radix tree bitmap infrastructure and replace it with a circular FIFO.
* Nothing is localized yet with this major surgery commit, which means radix nodes, hammer records, file data, and undo fifo elements are all being written to a single fifo. These elements will soon get their own abstracted fifos (and in particular, the undo elements will get a fixed-sized circular fifo and be considered temporary data).
* No sequence numbers or transaction spaces are generated yet.
* Create a 'hammer_off_t' type (64 bits). This type reserves 4 bits for a zone. Zones which encode volume numbers reserve another 8 bits, giving us a 52 bit byte offset able to represent up to 4096 TB per volume. Zones which do not encode volume numbers have 60 bits available for an abstracted offset, resulting in a maximum filesystem size of 2^60 bytes (1 MTB). Up to 15 zones can be encoded.
As of this commit only 2 zones are implemented to wrap up existing functionality.
* Adjust the B-Tree to use full 64 bit hammer offsets. Have one global B-Tree for the entire filesystem. The tree is no longer per-cluster.
* Scrap the recovery and spike code. Scrap the cluster and super-cluster code. Scrap those portions of the B-Tree code that dealt with spikes. Scrap those portions of the IO subsystem that dealt with marking a cluster open or closed.
* Expand the hammer_modify_*() functions to include a data range and add UNDO record generation. Do not implement buffer ordering dependancies yet (ordering issues are going change radically with the FIFO model).
show more ...
|
#
61aeeb33 |
| 03-Jan-2008 |
Matthew Dillon <dillon@dragonflybsd.org> |
HAMMER 15/many - user utility infrastructure, refactor alists, misc
* Abstract out userland access to HAMMER's on-disk structures in preparation for more userland work.
* Clean up compiler warnin
HAMMER 15/many - user utility infrastructure, refactor alists, misc
* Abstract out userland access to HAMMER's on-disk structures in preparation for more userland work.
* Clean up compiler warnings.
* Refactor the A-list recursion API. Use another bit code (10) to indicate the all-allocated & initialized state, verses an all-allocated & uninitialized state.
This allows an all-empty flag to propogate up the chain properly which in turn allows us to avoid flushing out dirty backing store for freed disk blocks and will eventually lead to freeing typed buffers back to the cluster's master a-list.
* Fix an edge case in the B-Tree code related to running out of space during an insertion search. If the insertion search ran out of space at a cluster boundary the spike code asserted because the parent B-Tree node wasn't in the same cluster as the node it thought it had to spike. (The root B-Tree node of a cluster cannot be spiked).
* Use a second cache pointer in the in-memory structure for directory inodes. The second cache will be used for inode lookups relative to the directory and will (eventually) greatly reduce the B-Tree search overhead required to stat directory elements.
show more ...
|
#
ed3afcca |
| 16-Oct-2007 |
Matthew Dillon <dillon@dragonflybsd.org> |
Add volume, super-cluster, cluster, and buffer abstractions to provide infrastructure for manipulating, reading, and writing various HAMMER filesystem buffer types.
Properly set up allocation hints
Add volume, super-cluster, cluster, and buffer abstractions to provide infrastructure for manipulating, reading, and writing various HAMMER filesystem buffer types.
Properly set up allocation hints and use the A-list's as-of feature.
Completely implement super-cluster A-list layering and cluster/buffer A-list layering.
(Preliminary) initialization of all primary on-disk structures and the root directory.
show more ...
|
#
9a8bf4a7 |
| 10-Oct-2007 |
Matthew Dillon <dillon@dragonflybsd.org> |
Initial commit of newfs_hammer - basic working skeleton for testing.
|