*BSD News Article 88254


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!swidir.switch.ch!news.grnet.gr!btnet-feed2!unlisys!fu-berlin.de!news.mathworks.com!newsfeed.internetmci.com!demos!news.uni-stuttgart.de!news.urz.uni-heidelberg.de!rz.uni-karlsruhe.de!not-for-mail
From: uk1o@rzstud2.rz.uni-karlsruhe.de (Felix Schroeter)
Newsgroups: comp.os.linux.misc,comp.os.linux.networking,comp.os.linux.setup,comp.unix.bsd.misc,comp.os.ms-windows.nt.advocacy,comp.os.os2.advocacy
Subject: Re: Linux vs whatever
Date: 4 Feb 1997 21:23:54 +0100
Organization: University of Karlsruhe, Germany
Lines: 30
Message-ID: <5d85sq$27u@rzstud2.rz.uni-karlsruhe.de>
References: <32DFFEAB.7704@usa.net> <5cphaj$qvg@cynic.portal.ca> <5d7rtu$ao9@rzstud2.rz.uni-karlsruhe.de> <5d81q1$8ls@cynic.portal.ca>
NNTP-Posting-Host: rzstud2.rz.uni-karlsruhe.de
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Xref: euryale.cc.adfa.oz.au comp.os.linux.misc:155950 comp.os.linux.networking:67156 comp.os.linux.setup:95312 comp.unix.bsd.misc:2217 comp.os.ms-windows.nt.advocacy:51799 comp.os.os2.advocacy:265441

Hello!

In article <5d81q1$8ls@cynic.portal.ca>,
Curt Sampson <cjs@cynic.portal.ca> wrote:
>In article <5d7rtu$ao9@rzstud2.rz.uni-karlsruhe.de>,
>Felix Schroeter <uk1o@rzstud2.rz.uni-karlsruhe.de> wrote:

>[...]
>>The 1KB write size was hardcoded in the Linux (2.0.something) NFS
>>client implementation.
>[...]

>Try an NFS test with 8 KB blocks, and you'll see just how broken
>the TCP/IP implementation is.

How do I do that? Patch the kernel or is there an easier way?

>                              There's a very good reason that Linux
>uses 1 KB blocks for NFS; the stack will crawl on 8 KB blocks
>because it has to do an extra copy of all the data every time it
>reassembles the fragments. (I described this in detail in another
>post.)

Hmmm. Does that adversary effect matter more than the adversary effect
of *many* *synchronous* writes (yielding a write "performance" of
about 35 kB/sec)?

>cjs

Regards, Felix.