From: Vincent Roqueta <vincent.roqueta@ext.bull.net>
To: linux-kernel@vger.kernel.org
Subject: UDP and e1000 : Simple test, little bugs.
Date: Tue, 15 Feb 2005 11:08:46 +0100 [thread overview]
Message-ID: <200502151108.46768.vincent.roqueta@ext.bull.net> (raw)
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)
Network card is the intel e1000 ethernet card. I tried with rxpolling turned
on and off. Bug doesnot appear in loopback.
Anyone interrested in that?
Vincent ROQUETA
/****************************************
* Simple Client
* Port : 9999
* argument 1 : buffer size to send
* argument 2 : server ip adress.
****************************************/
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <stdio.h>
int main (int argc, char * argv[])
{
int sock;
struct sockaddr_in name;
int size;
char *ip;
size=atoi(argv[1]);
ip=argv[2];
char DATA[size];
sock = socket (AF_INET, SOCK_DGRAM, 0);
if (sock < 0)
{
perror ("socket");
return 1;
}
bzero (&name, sizeof (name));
memset(DATA, 'A', sizeof(DATA));
name.sin_family = AF_INET;
name.sin_addr.s_addr = inet_addr (ip);
name.sin_port = htons(9999);
fprintf(stdout, "client UDP, port: %d\n", ntohs(name.sin_port));
if(sendto(sock,DATA,sizeof(DATA),0,(struct sockaddr
*)&name,sizeof(name))<0)
{
perror("sendto");
close(sock);
return 1;
} close(sock);
return 0;
}
/********************************************
* Simple server
* port 9999
********************************************/
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <stdio.h>
int main (int argc, char * argv[])
{
int sock;
size_t length;
struct sockaddr_in name;
char buf [1024];
int nbr=0;
while (1)
{
bzero (&name, sizeof (name));
sock = socket (AF_INET, SOCK_DGRAM, 0);
if (sock < 0)
{
perror ("socket");
return 1;
}
name.sin_family = AF_INET;
name.sin_addr.s_addr = INADDR_ANY;
name.sin_port = htons(9999);
if (bind (sock, (struct sockaddr *)&name, sizeof (name)) < 0)
{
perror ("bind");
close (sock);
return 1;
}
if (getsockname (sock, (struct sockaddr *)&name, &length) < 0)
{
perror ("getsockname");
close (sock);
return 1;
}
printf ("Socket UDP port #%d\n", ntohs (name.sin_port));
nbr++;
printf("read nb%d\n",nbr);
if(read(sock, buf, 1024)<0)
{
perror ("read");
close (sock);
return 1;
}
printf ("%s", buf);
printf("\n");
close (sock);
}
return 0;
}
next reply other threads:[~2005-02-15 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 10:08 Vincent Roqueta [this message]
2005-02-15 10:34 ` Vincent Roqueta
2005-02-18 0:28 ` Ben Greear
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=200502151108.46768.vincent.roqueta@ext.bull.net \
--to=vincent.roqueta@ext.bull.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®