From: Vincent Roqueta <vincent.roqueta@ext.bull.net>
To: Andi Kleen <ak@muc.de>
Cc: netdev@oss.sgi.com
Subject: Re: IP More Fragements bit problem.
Date: Mon, 14 Feb 2005 09:27:38 +0100 [thread overview]
Message-ID: <200502140927.38950.vincent.roqueta@ext.bull.net> (raw)
In-Reply-To: <m1braruf85.fsf@muc.de>
Le vendredi 11 Février 2005 19:24, vous avez écrit :
> 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.
Yes, I am sure testing with NFSv3 over UDP.
I can send you traces seen by AIX.
> And ping uses the same code to fragment as NFS sunrpc
> over UDP.
Ok.
> 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.
I don't have that :(
> Also why are you testing NFSv4 over UDP anyways? I thought
> everybody was finally running it over TCP now.
I am not testing NFSv4 over UDP, I am doing NFSv3 tests over UDP to compare
performances between NFSv4 and NFSv3, and some interoperablity testing on NFS
(v3 and v4). That the last tests that does not work fine.
Vincent
next prev parent reply other threads:[~2005-02-14 8:27 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
2005-02-14 8:27 ` Vincent Roqueta [this message]
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=200502140927.38950.vincent.roqueta@ext.bull.net \
--to=vincent.roqueta@ext.bull.net \
--cc=ak@muc.de \
--cc=netdev@oss.sgi.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 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).