Re: IPv6: Connection reset/timeout under heavy load

2007-03-28 Thread YOSHIFUJI Hideaki / 吉藤英明
In article <[EMAIL PROTECTED]> (at Wed, 28 Mar 2007 02:26:24 -0700 (PDT)), 
David Miller <[EMAIL PROTECTED]> says:

> > http://www.linux-ipv6.org/gitweb/gitweb.cgi?p=gitroot/yoshfuji/linux-2.6-fix.git;a=commit;h=33a79bba0cc2f197b46cc54182f94c31ff6ad334
> > 
> > I hope this patch will go in 2.6.16-stable...
> 
> Please forward this patch to Adrian Bunk ([EMAIL PROTECTED]),
> he will definitely add it to 2.6.16-stable for you.

I will do it again...

--yoshfuji
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: IPv6: Connection reset/timeout under heavy load

2007-03-28 Thread David Miller
From: YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL PROTECTED]>
Date: Wed, 28 Mar 2007 18:23:34 +0900 (JST)

> In article <[EMAIL PROTECTED]> (at Wed, 28 Mar 2007 10:48:27 +0200), Agoston 
> Horvath <[EMAIL PROTECTED]> says:
> 
> > YOSHIFUJI Hideaki / 吉藤英明 wrote:
> > > Would you test with latest kernel, if possible, please?
> > 
> > For the archive: switching to 2.6.20.4 fixed this problem.
> 
> Thank you for your report.
> 
> I guess the following change will fix the issue for 2.6.16.y:
> http://www.linux-ipv6.org/gitweb/gitweb.cgi?p=gitroot/yoshfuji/linux-2.6-fix.git;a=commit;h=33a79bba0cc2f197b46cc54182f94c31ff6ad334
> 
> I hope this patch will go in 2.6.16-stable...

Please forward this patch to Adrian Bunk ([EMAIL PROTECTED]),
he will definitely add it to 2.6.16-stable for you.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: IPv6: Connection reset/timeout under heavy load

2007-03-28 Thread YOSHIFUJI Hideaki / 吉藤英明
In article <[EMAIL PROTECTED]> (at Wed, 28 Mar 2007 10:48:27 +0200), Agoston 
Horvath <[EMAIL PROTECTED]> says:

> YOSHIFUJI Hideaki / 吉藤英明 wrote:
> > Would you test with latest kernel, if possible, please?
> 
> For the archive: switching to 2.6.20.4 fixed this problem.

Thank you for your report.

I guess the following change will fix the issue for 2.6.16.y:
http://www.linux-ipv6.org/gitweb/gitweb.cgi?p=gitroot/yoshfuji/linux-2.6-fix.git;a=commit;h=33a79bba0cc2f197b46cc54182f94c31ff6ad334

I hope this patch will go in 2.6.16-stable...

Regards,

--yoshfuji
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: IPv6: Connection reset/timeout under heavy load

2007-03-28 Thread Agoston Horvath
YOSHIFUJI Hideaki / 吉藤英明 wrote:
> Would you test with latest kernel, if possible, please?

For the archive: switching to 2.6.20.4 fixed this problem.

Thanks!

Agoston
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


IPv6: Connection reset/timeout under heavy load

2007-03-27 Thread Agoston Horvath
Hello,

I'm trying to add ipv6 support to the RIPE whois-server. I'm going with the 
dual-stack address familiy independent solution (/proc/sys/net/ipv6/bindv6only 
is set to 0).
I've written a small piece of code which tests how the server behaves under 
heavy load. It basically creates a specified number of threads and hammers the 
query port of the server with logged real-world queries. This works fine over 
ipv4. But if I switch to ipv6 (meaning, instead of the ipv4 address of eth0, I 
give the ipv6 one to getaddrinfo()), strange connection reset/timeout problems 
arise. This is especially strange because it's all AF-independent, so the very 
same piece of code runs fine for ipv4, but fails for ipv6.

I've created a small excerpt of the connection code (see attachment), which can 
be used to reproduce the problem. I've played around with number of 
clients/servers and the number of threads, and came to the conclusion that the 
problem is most probably in either in libc or in the kernel.
Strangest thing is that if I set the client to use 1 thread only, it works 
well. If I either start 2 pieces of 1-threaded clients or 1 piece of 2-threaded 
client, they start throwing errors.

I've even fiddled with sysctls tcp_fin_timeout, tcp_tw_recycle and 
tcp_tw_reuse, but it didn't change anything. Setting SO_LINGER to a smaller 
value also didn't help.

I'm using kernel 2.6.16.29, libc is 2.3.2.ds1-22sarge5. However, same result 
was achieved using kernel version 2.6.13 on the same box.

I'm out of further ideas. If anyone can give me some pointers about what could 
be wrong, please, don't spare me.

Thanks,
Agoston



load_test.tar.gz
Description: GNU Zip compressed data


Re: IPv6: Connection reset/timeout under heavy load

2007-03-27 Thread Agoston Horvath
(Let's take it off linux-kernel; I've subscribed to netdev)


YOSHIFUJI Hideaki / 吉藤英明 wrote:
> Would you test with latest kernel, if possible, please?

I'll give it a try; however, this might take a couple of days (I have no auth 
to replace the kernel on the box :( ).

Cheers,
Agoston
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: IPv6: Connection reset/timeout under heavy load

2007-03-27 Thread YOSHIFUJI Hideaki / 吉藤英明
Hello.

(CC: netdev added.)

In article <[EMAIL PROTECTED]> (at Tue, 27 Mar 2007 11:45:46 +0200), Agoston 
Horvath <[EMAIL PROTECTED]> says:

> I'm using kernel 2.6.16.29, libc is 2.3.2.ds1-22sarge5. However, same result 
> was achieved using kernel version 2.6.13 on the same box.
> 
> I'm out of further ideas. If anyone can give me some pointers about what 
> could be wrong, please, don't spare me.

Would you test with latest kernel, if possible, please?

--yoshfuji
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html