LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: vandrove@vc.cvut.cz, LKML <linux-kernel@vger.kernel.org>
Subject: Re: ncpfs and TCP vs UDP
Date: Sat, 27 Jan 2007 17:06:57 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.4.61.0701271706230.22295@yvahk01.tjqt.qr> (raw)
In-Reply-To: <45BB69BE.5060403@drzeus.cx>


>> Well, probably the same reason as NFS over UDP is discouraged. See nfs(5)
>> section WARNINGS (in short: IP fragment ID can wrap quite fast on Gigabit)
>
>I have no such warning in my nfs(5), but I am aware of this yes.
>Somewhat amusing that both nfs and ncpfs tend to default to using udp
>with this in mind. ;)

nfs has already been "fixed" to prefer tcp over udp (i.e. the default is tcp)


	-`J'
-- 

      reply	other threads:[~2007-01-27 16:08 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
2007-01-27 14:51   ` Jan Engelhardt
2007-01-27 15:03     ` Pierre Ossman
2007-01-27 16:06       ` Jan Engelhardt [this message]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=Pine.LNX.4.61.0701271706230.22295@yvahk01.tjqt.qr \
    --to=jengelh@linux01.gwdg.de \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    --subject='Re: ncpfs and TCP vs UDP' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).