LKML Archive on
help / color / mirror / Atom feed
To: Pierre Ossman <>
Cc: LKML <>
Subject: Re: ncpfs and TCP vs UDP
Date: Fri, 26 Jan 2007 22:20:50 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Quoting Pierre Ossman <>:

> Hi Petr,


> I was hoping you could give me some input on another concern I have.
> Which of TCP and UDP is the preferred transport for NCP? The client for
> Windows seems to use TCP, which would suggest that that is the most
> tested dialect. I also did a quick test with bonnie++:

TCP is definitely preferred.  There are couple of reasons why you should prefer TCP:

(1) There is server configuration option to disable NCP/UDP.  You cannot disable
NCP/TCP that easily.

(2) TCP (NCP over TCP) retransmits only missing data, and it can ask for
retransmit much sooner as it knows what link latency is.  NCP/UDP can only ask
for complete packet retransmission, and it has no good idea what's link latency
because there is no ACK from server when it receives request - you can only
resend after usual link latency + time for process request, so you'll wait
longer for retransmit, and on retransmit you need to send again complete request
(which can be 64KB of data if you use 64KB buffer size...)

(3) To avoid problems with retransmits ncpfs uses default buffer size 60KB for
TCP (SOCK_STREAM), while 1KB for UDP/IPX (it must be multiple of sector size, so
using 1.4KB is not an option).  So if you read 1 page, you get 1 request/reply
when using TCP, but 4 requests/replies in UDP/IPX.  And as all this is fully
synchronous, and for today's link latency is dominating factor, it will take 4
times longer...

(4) Theoretically with TCP you should never need retransmits as TCP takes care
of that.  Unfortunately due to server implementation you still cannot have more
than one request in flight (at least with NW5 - I never tried it with NW6 as
spec says I should not do that, and NW5 implementation agreed with spec).

> Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
>         500M  1569  19  1714  10   826   9  1414  18  1569   9  65.2   3
>              ------Sequential Create------ --------Random Create--------
>              -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
>        files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
>           16   460  14   897  16   556  15   491  15  1131  13   320   6

What was 'Block' size ?  For 1KB block size you should get more or less same
speed for TCP and UDP.  If you have link with big latency and big throughput,
then for 2KB block TCP should be 2 times faster, for 60KB block 60 times faster,
and above 60KB block difference should stay on 1:60.

You can try bumping NCP/UDP block size to 60KB as well, but my exprience with
switches and NetWare is that in such cases you can get into situation with
deterministic packet loss - like that from 40 UDP packets sent back to back to
server every 12th gets lost - and if you resend, again 12th packet gets lost,
again and again until you have some luck, or until client decides that server is

  reply	other threads:[~2007-01-26 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26 15:54 Pierre Ossman
2007-01-26 21:20 ` vandrove [this message]
2007-01-27 14:51   ` Jan Engelhardt
2007-01-27 15:03     ` Pierre Ossman
2007-01-27 16:06       ` Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: ncpfs and TCP vs UDP' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).