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, v4.8.1 |
|
#
78418745 |
| 12-Apr-2017 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/*hammer: Use typedef'd for struct cache_info*
This is a part of series of commits started from 21e9e7d5ff in 2016. This is for userspace.
|
#
c17fa600 |
| 12-Apr-2017 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/*hammer: Use typedef'd for struct buffer_info*
This is a part of series of commits started from 21e9e7d5ff in 2016. This is for userspace.
|
#
f254e677 |
| 10-Apr-2017 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Partly bring back removed braces from 52e2f1b5
based on comments from dillon@.
(dillon) three types, yah. (1) multi-line condition in if(), (2) if TRUE or FALSE body spans more than o
sbin/hammer: Partly bring back removed braces from 52e2f1b5
based on comments from dillon@.
(dillon) three types, yah. (1) multi-line condition in if(), (2) if TRUE or FALSE body spans more than one line, put braces around both (dillon) (including if a comment is part of the body)
show more ...
|
#
52e2f1b5 |
| 09-Apr-2017 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Cleanup blocks with a single statement
This commit basically does the same as what Linux kernel's coding style mentions for braces, which is basically the same with BSDs. https://github
sbin/hammer: Cleanup blocks with a single statement
This commit basically does the same as what Linux kernel's coding style mentions for braces, which is basically the same with BSDs. https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst#3-placing-braces-and-spaces
No diff in sbin/hammer/hammer binary when assert(3) is disabled.
show more ...
|
Revision tags: v4.8.0, v4.6.2, v4.9.0, v4.8.0rc |
|
#
281de955 |
| 16-Dec-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Refactor hammer_cache_flush()
|
#
e827d884 |
| 16-Dec-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Remove redundant cache counter NCache
Incrementation and decrementation of NCache is always aligned with CacheUse in a single thread program like /sbin/hammer, so this cache counter isn
sbin/hammer: Remove redundant cache counter NCache
Incrementation and decrementation of NCache is always aligned with CacheUse in a single thread program like /sbin/hammer, so this cache counter isn't necessary.
show more ...
|
#
62997e7b |
| 16-Dec-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Use HAMMER_BUFSIZE to calculate CacheMax
CacheMax is to be compared with multiple of HAMMER_BUFSIZE, so use HAMMER_BUFSIZE to initialize CacheMax.
|
Revision tags: v4.6.1 |
|
#
6c7ae023 |
| 02-Sep-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Remove hammer_cache_set()
|
#
7603683a |
| 01-Sep-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Make use of struct buffer_info::cache at offset 0
No need to hold a pointer to each other.
|
#
25ee129e |
| 14-Aug-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/newfs_hammer: Add -C option from hammer(8)
Just to support the same options given that these are both based on the same volume/buffer structure.
|
Revision tags: v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0 |
|
#
6456a4a4 |
| 04-Jun-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Remove debug printfs
These debug printfs are no longer really used for anything and probably by anyone as /sbin/hammer is stable enough.
These printfs generate tons of output to stderr
sbin/hammer: Remove debug printfs
These debug printfs are no longer really used for anything and probably by anyone as /sbin/hammer is stable enough.
These printfs generate tons of output to stderr, so it would be more convenient to just add some printfs to wherever necessary or use gdb for whatever issues found, rather than using these.
show more ...
|
Revision tags: v4.4.3 |
|
#
19c60b7c |
| 22-Mar-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Remove unused buffer 'type' in cache
HAMMER userspace cache is only used by general ondisk buffer. Ondisk volume header doesn't use the cache structure. Each program always has to expli
sbin/hammer: Remove unused buffer 'type' in cache
HAMMER userspace cache is only used by general ondisk buffer. Ondisk volume header doesn't use the cache structure. Each program always has to explicitly flush ondisk volume header.
This commit removes buffer 'type' from cache structure since 'type' is always general ondisk buffer (non-volume buffer).
show more ...
|
Revision tags: v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc |
|
#
9c8b568e |
| 07-Sep-2015 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Cleanup header includes regarding hammer_util.h
|
#
b45803e3 |
| 12-Aug-2015 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
hammer: Conform to style(9)
Also * Remove header includes that are already included by common hammer headers (of either userspace or kernel). * Add "#include <sys/vnode.h>" to sys/vfs/fifofs/fifo.
hammer: Conform to style(9)
Also * Remove header includes that are already included by common hammer headers (of either userspace or kernel). * Add "#include <sys/vnode.h>" to sys/vfs/fifofs/fifo.h.
show more ...
|
Revision tags: v4.2.4, v4.3.1 |
|
#
db8d09c1 |
| 24-Jul-2015 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Enable AssertOnFailure on -d for hammer show/checkmap
|
Revision tags: v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5 |
|
#
ef5468da |
| 16-Mar-2015 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Properly set counter in cache flushing loop
- This local variable 'count' being reset to 0 was probably intended to be set to 1, because otherwise --count; right after this makes it
sbin/hammer: Properly set counter in cache flushing loop
- This local variable 'count' being reset to 0 was probably intended to be set to 1, because otherwise --count; right after this makes it negative (which takes extra count before next CacheMax expansion). This makes no difference to results of hammer commands.
show more ...
|
#
1d05d4e0 |
| 16-Mar-2015 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Use existing function hammer_cache_used()
- Use existing function hammer_cache_used() for list operation.
|
#
d75d1dc9 |
| 14-Mar-2015 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Properly break from cache flush loop
- hammer_cache_flush() needs to keep track of the first element that was pushed back to tail of the list (ref!=0), and break from the loop if it
sbin/hammer: Properly break from cache flush loop
- hammer_cache_flush() needs to keep track of the first element that was pushed back to tail of the list (ref!=0), and break from the loop if it hits that element for the second time.
- It's currently working without above check because it breaks from the loop after it has accomplished 'target'. If this function was changed to release unlimited number of cache then it'll loop forever unless tracking those that can't be released (ref!=0).
show more ...
|
#
c2f57ae2 |
| 14-Mar-2015 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sbin/hammer: Add debug printf on cache flushing
- Add debug fprintf to stderr on cache flushing that shows the number of buffers released.
|
Revision tags: 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 |
|
#
84e57c2c |
| 26-Sep-2011 |
Thomas Nikolajsen <thomas@dragonflybsd.org> |
hammer(8): whitespace cleanup: delete blank at end of line
|
Revision tags: 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 |
|
#
b46b99bf |
| 20-Jun-2009 |
Matthew Dillon <dillon@apollo.backplane.com> |
HAMMER UTILITY - reorg cache, add -C, document blockmap and show command.
* Reorganize the way the local block cache works (in the utility, not the filesystem). Add the -C option to specify cache
HAMMER UTILITY - reorg cache, add -C, document blockmap and show command.
* Reorganize the way the local block cache works (in the utility, not the filesystem). Add the -C option to specify cache size and read-ahead.
* Document the blockmap command and enhance the documentation for the show command.
show more ...
|
#
0faa08a1 |
| 19-Jun-2009 |
Matthew Dillon <dillon@apollo.backplane.com> |
HAMMER UTIL - Add -C cachesize option to improve the 'show' command.
* Allows the default in-memory cache size of 16m to be changed.
|
Revision tags: v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1, v2.0.1 |
|
#
ac76a28d |
| 16-May-2008 |
Matthew Dillon <dillon@dragonflybsd.org> |
HAMMER Utilities: Stabilization pass.
* Fix a bug in 'hammer show' which caused the cache to expand indefinitely.
|
#
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 ...
|