public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Vincent Roqueta <vincent.roqueta@ext.bull.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UDP and e1000 : Simple test,  little bugs.
Date: Thu, 17 Feb 2005 16:28:51 -0800	[thread overview]
Message-ID: <421536C3.7050903@candelatech.com> (raw)
In-Reply-To: <200502151108.46768.vincent.roqueta@ext.bull.net>

Vincent Roqueta wrote:
> Hello all,
> 
> I am working on NFS interoperabiity and I experiment some problems with UDP. 
> The problem appear between the linux 2.6.10rc1 and 2.6.10rc2, and is still 
> present in the last kernel (2.6.11rc3)
> 
> With NFSv3:
> Client send a 32k file splited into 22 IP fragments. The problem is the server 
> only receive 17 fragments.
> More investigation tell me that the server reveive 17 fragments because the 
> client only send 17  IP fragments.
> 
> As the NFS client code is exactly the same between the 2.6.10rc1 and 2.6.10rc2 
> I tried to write a simple UDP client server, to be sure there is no relation 
> between this bug and NFS.
> 
> Client create a buffer of X bytes and fill it with the 'A' symbol. Then it 
> write it over a udp socket (sendto).
> Server read the first 1024KB sent.
> 
> If X is <26000 the write is done with sucess.
> Else it fail. (Typicaly for a 32KB size, as for NFS)

Try setting the socket send buffer size larger.  By default it's
quite small, and so it may not accept a large UDP frame.

Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      parent reply	other threads:[~2005-02-18  0:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15 10:08 UDP and e1000 : Simple test, little bugs Vincent Roqueta
2005-02-15 10:34 ` Vincent Roqueta
2005-02-18  0:28 ` Ben Greear [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=421536C3.7050903@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox