From: Andi Kleen <ak@muc.de>
To: Vincent Roqueta <vincent.roqueta@ext.bull.net>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Tony Reix <Tony.Reix@Bull.Net>,
netdev@oss.sgi.com
Subject: Re: IP More Fragements bit problem.
Date: Fri, 11 Feb 2005 19:24:42 +0100 [thread overview]
Message-ID: <m1braruf85.fsf@muc.de> (raw)
In-Reply-To: <200502111708.16024.vincent.roqueta@ext.bull.net> (Vincent Roqueta's message of "Fri, 11 Feb 2005 17:08:16 +0100")
Vincent Roqueta <vincent.roqueta@ext.bull.net> writes:
> D + MF
> *DELAY*
> A + MF
> B + MF
> C + MF
> D + MF
> *DELAY*
> ...
>
> After a while AIX destroy first fragments because of the IP fragements life
> time. Trond Myklebust said me you can do anything for that?
Are you sure? I tested 2.6.10rc3 and it works correctly for
me with ping. The algorithm in ip_fragment() looks good too
from visual inspection.
And ping uses the same code to fragment as NFS sunrpc
over UDP.
19:15:24.100934 averell > trent: (frag 64564:1480@1480+)
19:15:24.100938 averell > trent: (frag 64564:1480@2960+)
19:15:24.100943 averell > trent: (frag 64564:1480@4440+)
19:15:24.100947 averell > trent: (frag 64564:1480@5920+)
19:15:24.100951 averell > trent: (frag 64564:1480@7400+)
19:15:24.100957 averell > trent: (frag 64564:1128@8880) <--- No MF.
Also why are you testing NFSv4 over UDP anyways? I thought
everybody was finally running it over TCP now.
-Andi
next prev parent reply other threads:[~2005-02-11 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 16:08 IP More Fragements bit problem Vincent Roqueta
2005-02-11 18:24 ` Andi Kleen [this message]
2005-02-14 8:27 ` Vincent Roqueta
2005-02-11 18:44 ` Nivedita Singhvi
2005-02-14 8:29 ` Vincent Roqueta
2005-02-14 12:37 ` Vincent Roqueta
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=m1braruf85.fsf@muc.de \
--to=ak@muc.de \
--cc=Tony.Reix@Bull.Net \
--cc=netdev@oss.sgi.com \
--cc=trond.myklebust@fys.uio.no \
--cc=vincent.roqueta@ext.bull.net \
/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.