jeff 285c3f355c - Handle the truncation of an inode with an effective link count of 0 in ... the context of the process that reduced the effective count. Previously all truncation as a result of unlink happened in the softdep flush thread. This had the effect of being impossible to rate limit properly with the journal code. Now the process issuing unlinks is suspended when the journal files. This has a side-effect of improving rm performance by allowing more concurrent work. - Handle two cases in inactive, one for effnlink == 0 and another when nlink finally reaches 0. - Eliminate the SPACECOUNTED related code since the truncation is no longer delayed. Discussed with: mckusick		2010-07-06 07:11:04 +00:00
..
ffs	- Handle the truncation of an inode with an effective link count of 0 in	2010-07-06 07:11:04 +00:00
ufs	- Handle the truncation of an inode with an effective link count of 0 in	2010-07-06 07:11:04 +00:00