> > The culprit turned out to be an inherited CONFIG_NFS_DIRECTIO
> > setting. Having the client kernel (2.4.20rc2aa1) this option
> > turned off, performance is stable 4 MB/sec (server hasn't
> > changed). This is almost twice as good as with 2.4.19-rmap14b.
> Huh? Sounds like something is seriously screwed up in your
> kernel build then. CONFIG_NFS_DIRECTIO should should result in 2
> things only: [...] None of the ordinary NFS read and write code
> paths should be affected by the above.
Well, weird as it may seem, this is what happened. I compiled
2.4.20rc2aa1 with my .config, NFS sucked. make menuconfig, turned
off CONFIG_NFS_DIRECTIO, make -j2 bzImage modules modules_install
(no compiler errors), install kernel, lilo, reboot, NFS flies.
Confirmed on other machine as well. gcc is 3.2.1 (Debian sid).
Wish to seek more input on the case?
Peter
--
.+'''+. .+'''+. .+'''+. .+'''+. .+''
Kelemen Péter / \ / \ / fuji@elte.hu
.+' `+...+' `+...+' `+...+' `+...+'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/