Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*analysis\s+of\s+TCP\s+window\s+size\s+issues\s+still\s+around\s+\-\s+several\s+reports\s+\/\s+SACK\s+involved\?\s*$/: 14 ]

Total 14 documents matching your query.

1. analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: xxxx>
Date: Tue, 6 Jul 2004 11:35:03 +0200
People, There are still persistent reports of TCP problems, even after patching away the memory_pressure pointer problem. From one trace I've seen, by Alessandro Suardi, but I lack the SACK knowledge
/archives/netdev/2004-07/msg00121.html (14,633 bytes)

2. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: @xxxxxxx>
Date: Tue, 6 Jul 2004 06:30:51 -0600 (MDT)
Hi all, sorry about the silly formatting, but the webmail client isn't really nice in this respect :( Further data points: -bk18 built with GCC 3.4.1 still hangs talking to most of the world except g
/archives/netdev/2004-07/msg00124.html (13,416 bytes)

3. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: xxxxxxxxxx>
Date: Tue, 6 Jul 2004 14:42:54 +0200
I juist built 2.6.7-mm6 in an attempt to reproduce your problems but I can't see them, can you check with that version too? Is this the 5mb binary kernel module blob version? Can you reproduce the bu
/archives/netdev/2004-07/msg00128.html (9,907 bytes)

4. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: avid S. Miller" <davem@xxxxxxxxxx>
Date: Tue, 6 Jul 2004 13:19:55 -0700
tcpdump's behavior is correct, it's just reporting the raw window field in the TCP header, unscaled, and that is fine. In fact I'd rather it do this, so that diagnosing dumps are easier. If tcpdump t
/archives/netdev/2004-07/msg00149.html (11,787 bytes)

5. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: en Hemminger <shemminger@xxxxxxxx>
Date: Tue, 6 Jul 2004 13:31:22 -0700
That's great, thanks a lot.
/archives/netdev/2004-07/msg00154.html (11,077 bytes)

6. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: en Hemminger <shemminger@xxxxxxxx>
Date: Tue, 6 Jul 2004 22:27:08 +0200
True - it might want to print '43 (*128=5706)' or something like that. I have an appointment with Alessandro tomorrow evening at 11PM CEST to do just that. It sounds like window scaling may become ye
/archives/netdev/2004-07/msg00163.html (12,184 bytes)

7. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: d S. Miller" <davem@xxxxxxxxxx>
Date: Wed, 07 Jul 2004 23:25:38 +0200
bert hubert wrote: On Tue, Jul 06, 2004 at 01:19:55PM -0700, David S. Miller wrote: rather it do this, so that diagnosing dumps are easier. If tcpdump tries to be too clever, scaling the window, then
/archives/netdev/2004-07/msg00233.html (12,159 bytes)

8. analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: bert hubert <ahu@xxxxxxx>
Date: Tue, 6 Jul 2004 11:35:03 +0200
People, There are still persistent reports of TCP problems, even after patching away the memory_pressure pointer problem. From one trace I've seen, by Alessandro Suardi, but I lack the SACK knowledge
/archives/netdev/2004-07/msg00937.html (15,115 bytes)

9. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: ALESSANDRO.SUARDI@xxxxxxxxxx
Date: Tue, 6 Jul 2004 06:30:51 -0600 (MDT)
Hi all, sorry about the silly formatting, but the webmail client isn't really nice in this respect :( Further data points: -bk18 built with GCC 3.4.1 still hangs talking to most of the world except g
/archives/netdev/2004-07/msg00940.html (13,506 bytes)

10. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: bert hubert <ahu@xxxxxxx>
Date: Tue, 6 Jul 2004 14:42:54 +0200
I juist built 2.6.7-mm6 in an attempt to reproduce your problems but I can't see them, can you check with that version too? Is this the 5mb binary kernel module blob version? Can you reproduce the bu
/archives/netdev/2004-07/msg00944.html (10,042 bytes)

11. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: "David S. Miller" <davem@xxxxxxxxxx>
Date: Tue, 6 Jul 2004 13:19:55 -0700
tcpdump's behavior is correct, it's just reporting the raw window field in the TCP header, unscaled, and that is fine. In fact I'd rather it do this, so that diagnosing dumps are easier. If tcpdump t
/archives/netdev/2004-07/msg00965.html (12,207 bytes)

12. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: "David S. Miller" <davem@xxxxxxxxxx>
Date: Tue, 6 Jul 2004 13:31:22 -0700
That's great, thanks a lot.
/archives/netdev/2004-07/msg00970.html (11,563 bytes)

13. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: bert hubert <ahu@xxxxxxx>
Date: Tue, 6 Jul 2004 22:27:08 +0200
True - it might want to print '43 (*128=5706)' or something like that. I have an appointment with Alessandro tomorrow evening at 11PM CEST to do just that. It sounds like window scaling may become ye
/archives/netdev/2004-07/msg00979.html (12,679 bytes)

14. Re: analysis of TCP window size issues still around - several reports / SACK involved? (score: 1)
Author: Alessandro Suardi <alessandro.suardi@xxxxxxxxxx>
Date: Wed, 07 Jul 2004 23:25:38 +0200
rather it do this, so that diagnosing dumps are easier. If tcpdump tries to be too clever, scaling the window, then I might end up chasing down a tcpdump bug rather than a TCP one :-) True - it migh
/archives/netdev/2004-07/msg01049.html (12,468 bytes)

Current List: 1 - 14
Page: [1]

This search system is powered by Namazu