From: Andi Kleen <ak@suse.de>
To: David Stevens <dlstevens@us.ibm.com>
Cc: netdev@oss.sgi.com, rusty@au1.ibm.com
Subject: Re: Fragment ID wrap workaround (read-only, untested).
Date: Thu, 15 Jul 2004 19:02:49 +0200 [thread overview]
Message-ID: <20040715190249.01a9c11e.ak@suse.de> (raw)
In-Reply-To: <OF6D39F992.163676EB-ON88256ED2.005AF110-88256ED2.005CC82F@us.ibm.com>
On Thu, 15 Jul 2004 09:54:53 -0700
David Stevens <dlstevens@us.ibm.com> wrote:
> I agree that NFS over UDP should be dead as soon as possible,
> and fragmentation in general not far behind it. They aren't quite
> dead yet; until they are, why not make them better behaved? And
> if your argument is that it isn't worth fixing because it isn't
I wouldn't go that far, just make extremly sure that any
solution works on slow links too. The problem I see
is that if you make the delay factor long enough to make
the extremly variable links not regress you risk
making the wrap on very fast links likely again.
-Andi
next prev parent reply other threads:[~2004-07-15 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 5:57 Fragment ID wrap workaround (read-only, untested) Rusty Russell (IBM)
2004-07-15 8:28 ` David Stevens
2004-07-15 9:27 ` Andi Kleen
2004-07-15 14:49 ` David Stevens
2004-07-15 16:24 ` John Heffner
2004-07-15 16:27 ` Andi Kleen
2004-07-15 16:54 ` David Stevens
2004-07-15 17:02 ` Andi Kleen [this message]
2004-07-27 12:38 ` Olaf Kirch
-- strict thread matches above, loose matches on Subject: below --
2004-07-15 6:36 Rusty Russell (IBM)
2004-07-15 17:34 ` Andi Kleen
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=20040715190249.01a9c11e.ak@suse.de \
--to=ak@suse.de \
--cc=dlstevens@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=rusty@au1.ibm.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.