Ian Dowse 4202b366fc Oops, when trying the dirhash sequential-access optimisation, ... compare the slot offset against the predicted offset, not a boolean flag. This typo effectively disabled the sequential optimisation, but was otherwise harmless. Not surprisingly, fixing this improves performance in the sequential access case. I am seeing a 7% speedup on one machine here; using dirhash when sequentially looking up directory entries is now about 5% faster instead of 2% slower than the non-dirhash case. Submitted by: KOIE Hidetaka <koie@suri.co.jp> MFC after: 1 week		2001-11-14 15:08:07 +00:00
..
ffs	Implement kern.maxvnodes. adjusting kern.maxvnodes now actually has a	2001-10-26 00:08:05 +00:00
ifs	KSE Milestone 2	2001-09-12 08:38:13 +00:00
ufs	Oops, when trying the dirhash sequential-access optimisation,	2001-11-14 15:08:07 +00:00