Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 22 Feb 2001 13:52:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 22 Feb 2001 13:51:56 -0500 Received: from palrel1.hp.com ([156.153.255.242]:13061 "HELO palrel1.hp.com") by vger.kernel.org with SMTP id ; Thu, 22 Feb 2001 13:51:47 -0500 Message-ID: <3A9556A7.D052D8A6@cup.hp.com> Date: Thu, 22 Feb 2001 10:12:55 -0800 From: Rick Jones Organization: the Unofficial HP X-Mailer: Mozilla 4.75 [en] (X11; U; HP-UX B.11.00 9000/785) X-Accept-Language: en MIME-Version: 1.0 To: Alan Cox Cc: Nye Liu , linux-kernel@vger.kernel.org Subject: Re: Very high bandwith packet based interface and performance problems In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Alan Cox wrote: > > > > TCP _requires_ the remote end ack every 2nd frame regardless of progress. > > > > um, I thought the spec says that ACK every 2nd segment is a SHOULD not a > > MUST? > > Yes its a SHOULD in RFC1122, but in any normal environment pretty much a > must and I know of no stack significantly violating it. I didn't know there was such a thing as a normal environment :) > RFC1122 also requires that your protocol stack SHOULD be able to leap tall > buldings at a single bound of course... And, of course my protocol stack does :) It is also a floor wax, AND a dessert topping!-) rick jones -- ftp://ftp.cup.hp.com/dist/networking/misc/rachel/ these opinions are mine, all mine; HP might not want them anyway... :) feel free to email, OR post, but please do NOT do BOTH... my email address is raj in the cup.hp.com domain... - 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/