author | Junio C Hamano <junkio@cox.net> | |
Fri, 20 Jan 2006 01:13:51 +0000 (17:13 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Sun, 22 Jan 2006 03:33:22 +0000 (19:33 -0800) | ||
commit | 35a730f01c6caba93d452fa938e7d93ffcc4cf25 | |
tree | ceeeafb38d09feb7bd0230fe85ac34c438ad0a33 | tree | snapshot |
parent | bdc37f5a817543fc5eaf16dd6f30dd7b821adc70 | commit | diff |
fsck-objects: support platforms without d_ino in struct dirent.
The d_ino field is only used for performance reasons in
fsck-objects. On a typical filesystem, i-number tends to have a
strong correlation with where the actual bits sit on the disk
platter, and we sort the entries to allow us scan things that
ought to be close together together.
If the platform lacks support for it, it is not a big deal.
Just do not use d_ino for sorting, and scan them unsorted.
Signed-off-by: Junio C Hamano <junkio@cox.net>
The d_ino field is only used for performance reasons in
fsck-objects. On a typical filesystem, i-number tends to have a
strong correlation with where the actual bits sit on the disk
platter, and we sort the entries to allow us scan things that
ought to be close together together.
If the platform lacks support for it, it is not a big deal.
Just do not use d_ino for sorting, and scan them unsorted.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Makefile | diff | blob | history | |
fsck-objects.c | diff | blob | history |