Searched hist:"82010 f9f" (Results 1 – 8 of 8) sorted by relevance
| /dragonfly/sys/vfs/hammer/ |
| H A D | hammer_transaction.c | 82010f9f Sun Dec 28 23:29:48 GMT 2008 Matthew Dillon <dillon@apollo.backplane.com> HAMMER performance and kernel memory issues.
* The flusher could stall-out due to deadlocks under certain heavy load
situations (blogbench -i1000 -o), causing the number of hammer inodes
to increase slowly until the kernel runs out of memory.
Fix this by detecting the condition and stalling the threads
causing the deadlocks instead for a short while. Any user thread
which blocked performing B-Tree node I/O is a candidate.
* Improve the stability of the inode reclaim heuristic which slows
down the creation of new inodes when too many disconnected hammer
inodes are present.
* Remove vfs.hammer.limit_iqueued - this sysctl is no longer used.
Reported-by: YONETANI Tomokazu <qhwt+dfly@les.ath.cx>
|
| H A D | hammer_cursor.c | 82010f9f Sun Dec 28 23:29:48 GMT 2008 Matthew Dillon <dillon@apollo.backplane.com> HAMMER performance and kernel memory issues.
* The flusher could stall-out due to deadlocks under certain heavy load
situations (blogbench -i1000 -o), causing the number of hammer inodes
to increase slowly until the kernel runs out of memory.
Fix this by detecting the condition and stalling the threads
causing the deadlocks instead for a short while. Any user thread
which blocked performing B-Tree node I/O is a candidate.
* Improve the stability of the inode reclaim heuristic which slows
down the creation of new inodes when too many disconnected hammer
inodes are present.
* Remove vfs.hammer.limit_iqueued - this sysctl is no longer used.
Reported-by: YONETANI Tomokazu <qhwt+dfly@les.ath.cx>
|
| H A D | hammer_flusher.c | 82010f9f Sun Dec 28 23:29:48 GMT 2008 Matthew Dillon <dillon@apollo.backplane.com> HAMMER performance and kernel memory issues.
* The flusher could stall-out due to deadlocks under certain heavy load
situations (blogbench -i1000 -o), causing the number of hammer inodes
to increase slowly until the kernel runs out of memory.
Fix this by detecting the condition and stalling the threads
causing the deadlocks instead for a short while. Any user thread
which blocked performing B-Tree node I/O is a candidate.
* Improve the stability of the inode reclaim heuristic which slows
down the creation of new inodes when too many disconnected hammer
inodes are present.
* Remove vfs.hammer.limit_iqueued - this sysctl is no longer used.
Reported-by: YONETANI Tomokazu <qhwt+dfly@les.ath.cx>
|
| H A D | hammer_btree.c | 82010f9f Sun Dec 28 23:29:48 GMT 2008 Matthew Dillon <dillon@apollo.backplane.com> HAMMER performance and kernel memory issues.
* The flusher could stall-out due to deadlocks under certain heavy load
situations (blogbench -i1000 -o), causing the number of hammer inodes
to increase slowly until the kernel runs out of memory.
Fix this by detecting the condition and stalling the threads
causing the deadlocks instead for a short while. Any user thread
which blocked performing B-Tree node I/O is a candidate.
* Improve the stability of the inode reclaim heuristic which slows
down the creation of new inodes when too many disconnected hammer
inodes are present.
* Remove vfs.hammer.limit_iqueued - this sysctl is no longer used.
Reported-by: YONETANI Tomokazu <qhwt+dfly@les.ath.cx>
|
| H A D | hammer_ondisk.c | 82010f9f Sun Dec 28 23:29:48 GMT 2008 Matthew Dillon <dillon@apollo.backplane.com> HAMMER performance and kernel memory issues.
* The flusher could stall-out due to deadlocks under certain heavy load
situations (blogbench -i1000 -o), causing the number of hammer inodes
to increase slowly until the kernel runs out of memory.
Fix this by detecting the condition and stalling the threads
causing the deadlocks instead for a short while. Any user thread
which blocked performing B-Tree node I/O is a candidate.
* Improve the stability of the inode reclaim heuristic which slows
down the creation of new inodes when too many disconnected hammer
inodes are present.
* Remove vfs.hammer.limit_iqueued - this sysctl is no longer used.
Reported-by: YONETANI Tomokazu <qhwt+dfly@les.ath.cx>
|
| H A D | hammer_vfsops.c | 82010f9f Sun Dec 28 23:29:48 GMT 2008 Matthew Dillon <dillon@apollo.backplane.com> HAMMER performance and kernel memory issues.
* The flusher could stall-out due to deadlocks under certain heavy load
situations (blogbench -i1000 -o), causing the number of hammer inodes
to increase slowly until the kernel runs out of memory.
Fix this by detecting the condition and stalling the threads
causing the deadlocks instead for a short while. Any user thread
which blocked performing B-Tree node I/O is a candidate.
* Improve the stability of the inode reclaim heuristic which slows
down the creation of new inodes when too many disconnected hammer
inodes are present.
* Remove vfs.hammer.limit_iqueued - this sysctl is no longer used.
Reported-by: YONETANI Tomokazu <qhwt+dfly@les.ath.cx>
|
| H A D | hammer_inode.c | 82010f9f Sun Dec 28 23:29:48 GMT 2008 Matthew Dillon <dillon@apollo.backplane.com> HAMMER performance and kernel memory issues.
* The flusher could stall-out due to deadlocks under certain heavy load
situations (blogbench -i1000 -o), causing the number of hammer inodes
to increase slowly until the kernel runs out of memory.
Fix this by detecting the condition and stalling the threads
causing the deadlocks instead for a short while. Any user thread
which blocked performing B-Tree node I/O is a candidate.
* Improve the stability of the inode reclaim heuristic which slows
down the creation of new inodes when too many disconnected hammer
inodes are present.
* Remove vfs.hammer.limit_iqueued - this sysctl is no longer used.
Reported-by: YONETANI Tomokazu <qhwt+dfly@les.ath.cx>
|
| H A D | hammer.h | 82010f9f Sun Dec 28 23:29:48 GMT 2008 Matthew Dillon <dillon@apollo.backplane.com> HAMMER performance and kernel memory issues.
* The flusher could stall-out due to deadlocks under certain heavy load
situations (blogbench -i1000 -o), causing the number of hammer inodes
to increase slowly until the kernel runs out of memory.
Fix this by detecting the condition and stalling the threads
causing the deadlocks instead for a short while. Any user thread
which blocked performing B-Tree node I/O is a candidate.
* Improve the stability of the inode reclaim heuristic which slows
down the creation of new inodes when too many disconnected hammer
inodes are present.
* Remove vfs.hammer.limit_iqueued - this sysctl is no longer used.
Reported-by: YONETANI Tomokazu <qhwt+dfly@les.ath.cx>
|