Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759124AbZAIXBi (ORCPT ); Fri, 9 Jan 2009 18:01:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754092AbZAIXB1 (ORCPT ); Fri, 9 Jan 2009 18:01:27 -0500 Received: from cs-studio.ru ([195.178.208.66]:51549 "EHLO tservice.net.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753414AbZAIXB0 (ORCPT ); Fri, 9 Jan 2009 18:01:26 -0500 Date: Sat, 10 Jan 2009 02:01:24 +0300 From: Evgeniy Polyakov To: Willy Tarreau Cc: Eric Dumazet , David Miller , ben@zeus.com, jarkao2@gmail.com, mingo@elte.hu, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, jens.axboe@oracle.com Subject: Re: [PATCH] tcp: splice as many packets as possible at once Message-ID: <20090109230124.GA11592@ioremap.net> References: <4966F2F4.9080901@cosmosbay.com> <49677074.5090802@cosmosbay.com> <20090109185448.GA1999@1wt.eu> <4967B8C5.10803@cosmosbay.com> <20090109212400.GA3727@1wt.eu> <20090109220737.GA4111@1wt.eu> <4967CBB9.1060403@cosmosbay.com> <20090109221744.GA4819@1wt.eu> <20090109224258.GA10257@ioremap.net> <20090109225010.GB4819@1wt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090109225010.GB4819@1wt.eu> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1005 Lines: 23 On Fri, Jan 09, 2009 at 11:50:10PM +0100, Willy Tarreau (w@1wt.eu) wrote: > Well, I'm now trying to educate myself on the send part. It's still > not very clear to me and I'd like to understand a little bit better > why we have this corruption problem and why there is a difference > between sending segments from memory and sending them from another > socket where they were already waiting. printks are the best choice, since you will get exactly what you are looking for instead of deciphering what developer or code told you. > I think I'll put printks everywhere and see what I can observe. > Knowing about the GSO/SG workaround already helps me enable/disable > the bug. I wish I could also be capable to disable the bugs... :) -- Evgeniy Polyakov -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/