Searched hist:"37 aa19df" (Results 1 – 6 of 6) sorted by relevance
| /dragonfly/sys/vfs/hammer2/ |
| H A D | hammer2_freemap.c | diff 37aa19df Tue Feb 28 05:22:53 GMT 2012 Matthew Dillon <dillon@apollo.backplane.com> hammer2 - more indirect block work, add advlock
* Fix several bugs in the indirect block code. Directories and files should
both now be able to expand properly. Except for an excessive dirty buffer
buildup (see 'bawrite' below), we can now create regular files linearly
and create sub-directory trees. e.g. cpdup is starting to show results.
* Fix an issue with readdir related to how ranged searches work (results
can be returned in any order within the range). Do a direct lookup of
the key before resorting to a range. Until we sort the keys this is not
going to work correctly in the face of concurrent deletions.
* Try conditionalizing bawrite() vs bdwrite() in the flush code, but there
are still major issues when NFS is used to back a VN device for testing
which can deadlock the system.
* Remove or conditionalize a bunch of debugging kprintfs.
|
| H A D | hammer2_inode.c | diff 37aa19df Tue Feb 28 05:22:53 GMT 2012 Matthew Dillon <dillon@apollo.backplane.com> hammer2 - more indirect block work, add advlock
* Fix several bugs in the indirect block code. Directories and files should
both now be able to expand properly. Except for an excessive dirty buffer
buildup (see 'bawrite' below), we can now create regular files linearly
and create sub-directory trees. e.g. cpdup is starting to show results.
* Fix an issue with readdir related to how ranged searches work (results
can be returned in any order within the range). Do a direct lookup of
the key before resorting to a range. Until we sort the keys this is not
going to work correctly in the face of concurrent deletions.
* Try conditionalizing bawrite() vs bdwrite() in the flush code, but there
are still major issues when NFS is used to back a VN device for testing
which can deadlock the system.
* Remove or conditionalize a bunch of debugging kprintfs.
|
| H A D | hammer2_vnops.c | diff 37aa19df Tue Feb 28 05:22:53 GMT 2012 Matthew Dillon <dillon@apollo.backplane.com> hammer2 - more indirect block work, add advlock
* Fix several bugs in the indirect block code. Directories and files should
both now be able to expand properly. Except for an excessive dirty buffer
buildup (see 'bawrite' below), we can now create regular files linearly
and create sub-directory trees. e.g. cpdup is starting to show results.
* Fix an issue with readdir related to how ranged searches work (results
can be returned in any order within the range). Do a direct lookup of
the key before resorting to a range. Until we sort the keys this is not
going to work correctly in the face of concurrent deletions.
* Try conditionalizing bawrite() vs bdwrite() in the flush code, but there
are still major issues when NFS is used to back a VN device for testing
which can deadlock the system.
* Remove or conditionalize a bunch of debugging kprintfs.
|
| H A D | hammer2_chain.c | diff 37aa19df Tue Feb 28 05:22:53 GMT 2012 Matthew Dillon <dillon@apollo.backplane.com> hammer2 - more indirect block work, add advlock
* Fix several bugs in the indirect block code. Directories and files should
both now be able to expand properly. Except for an excessive dirty buffer
buildup (see 'bawrite' below), we can now create regular files linearly
and create sub-directory trees. e.g. cpdup is starting to show results.
* Fix an issue with readdir related to how ranged searches work (results
can be returned in any order within the range). Do a direct lookup of
the key before resorting to a range. Until we sort the keys this is not
going to work correctly in the face of concurrent deletions.
* Try conditionalizing bawrite() vs bdwrite() in the flush code, but there
are still major issues when NFS is used to back a VN device for testing
which can deadlock the system.
* Remove or conditionalize a bunch of debugging kprintfs.
|
| H A D | hammer2_vfsops.c | diff 37aa19df Tue Feb 28 05:22:53 GMT 2012 Matthew Dillon <dillon@apollo.backplane.com> hammer2 - more indirect block work, add advlock
* Fix several bugs in the indirect block code. Directories and files should
both now be able to expand properly. Except for an excessive dirty buffer
buildup (see 'bawrite' below), we can now create regular files linearly
and create sub-directory trees. e.g. cpdup is starting to show results.
* Fix an issue with readdir related to how ranged searches work (results
can be returned in any order within the range). Do a direct lookup of
the key before resorting to a range. Until we sort the keys this is not
going to work correctly in the face of concurrent deletions.
* Try conditionalizing bawrite() vs bdwrite() in the flush code, but there
are still major issues when NFS is used to back a VN device for testing
which can deadlock the system.
* Remove or conditionalize a bunch of debugging kprintfs.
|
| H A D | hammer2.h | diff 37aa19df Tue Feb 28 05:22:53 GMT 2012 Matthew Dillon <dillon@apollo.backplane.com> hammer2 - more indirect block work, add advlock
* Fix several bugs in the indirect block code. Directories and files should
both now be able to expand properly. Except for an excessive dirty buffer
buildup (see 'bawrite' below), we can now create regular files linearly
and create sub-directory trees. e.g. cpdup is starting to show results.
* Fix an issue with readdir related to how ranged searches work (results
can be returned in any order within the range). Do a direct lookup of
the key before resorting to a range. Until we sort the keys this is not
going to work correctly in the face of concurrent deletions.
* Try conditionalizing bawrite() vs bdwrite() in the flush code, but there
are still major issues when NFS is used to back a VN device for testing
which can deadlock the system.
* Remove or conditionalize a bunch of debugging kprintfs.
|