This patch should only go in if 2.4.20 is 3 weeks or more away, 
otherwise it should wait for the next pre1.

It passes all of our testing, but it is the kind of code that is more 
likely than most to have elusive lurking bugs.  It cannot be tested in 
2.5 first because 2.5 is too broken at this particular moment.  For the 
lkml readers let me say that it also should not go onto any distros 
without three weeks of testing.;-)

It substantially reduces CPU consumption for large writes.  It does so 
by finally ridding the code of that 4k at a time write loop that 
performed a balancing operation and a block allocation for each 4k 
written.   This might be the last substantial patch from Namesys before 
V4.:)  Chris still has some patches that are substantive though which I 
hope he sends in very soon...

It also contains some trivial fixes in the second of the attachments 
from Oleg.

    Adding back mistakenly forgotten "attrs" mount option, fix a problem
    with displacing_large_files allocator option and fix a bug in remounting
    code on remount from readwarite to readwrite mode that can cause livelock
    if there was delayed unlinks scheduled on the filesystem.


Marcelo, since you know how long it will be until 2.4.20, you should 
decide if it will go in.  

Hans