Messages in this thread | | | Subject | Re: NFS performance ... | From | Trond Myklebust <> | Date | 28 Nov 2002 17:40:30 +0100 |
| |
>>>>> " " == KELEMEN Peter <fuji@elte.hu> writes:
> * Marc-Christian Petersen (m.c.p@wolk-project.de) [20021124 > 15:23]: > Marc, Andrea,
>> I think Andrea and me have something in our kernels that may >> cause it. For me I don't know what that can be. I even have no >> idea what it can be :(
> 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:
- direct.c gets compiled.
- the 'direct_IO' address space operation gets defined, so that the VFS knows what to do with files that get opened with the O_DIRECT flag.
None of the ordinary NFS read and write code paths should be affected by the above.
Cheers, Trond - 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/
| |