From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?D=E2niel?= Fraga Subject: Re: [PATCH] tcp FRTO: in-order-only "TCP proxy" fragility workaround Date: Mon, 22 Sep 2008 13:13:39 -0300 Message-ID: <20080922131339.79abf28a@tux> References: <20080819213417.45133573@tux> <20080826141812.589848a0@tux> <20080828184919.611dd578@tux> <20080830035650.42be37d7@tux> <20080907051718.58bf133d@tux> <20080908172043.0d25a427@tux> <20080911143006.2f516569@tux> <20080913203117.2a55ea2c@tux> <20080916112411.062fa615@tux> <20080918173554.1f874238@tux> <20080922012338.694d30b0@tux> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: David Miller , thomas.jarosch@intra2net.com, billfink@mindspring.com, Netdev , Patrick Hardy , netfilter-devel@vger.kernel.org, kadlec@blackhole.kfki.hu To: "Ilpo =?ISO-8859-1?Q?J=E4rvinen?=" Return-path: In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Mon, 22 Sep 2008 14:22:12 +0300 (EEST) "Ilpo J=E4rvinen" wrote: > It seems that next sensible step is to just obtain a full strace to s= ee=20 > what actually took place during those long minutes if anything (it's=20 > better that you keep that log private and just use grep over it on=20 > request). ...A full strace might grow huge though. Also, for strace u= se=20 > -tt instead of -t to get more accurate timestamps and add -T. >=20 > When you get the stall next time, please also check that the processe= s are=20 > actually sleeping instead of looping like crazy in some buggy userspa= ce=20 > code :-) (obviously before resolving it with nmap). >=20 > When using nmap to resolve, take note on exact timestamp (including=20 > seconds). E.g.,=20 > $ date > nmap.ts; nmap ... Thanks! Today I'm lucky. I got the stall fast. It seems that it happens more frequently as more connections are made. What should I grep? --=20 -- To unsubscribe from this list: send the line "unsubscribe netfilter-dev= el" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html