Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 30 Apr 2001 17:48:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 30 Apr 2001 17:47:43 -0400 Received: from twinlark.arctic.org ([204.107.140.52]:38412 "HELO twinlark.arctic.org") by vger.kernel.org with SMTP id ; Mon, 30 Apr 2001 17:47:36 -0400 Date: Mon, 30 Apr 2001 14:47:35 -0700 (PDT) From: dean gaudet To: "David S. Miller" , Fabio Riccardi cc: Ingo Molnar , , Alan Cox , Christopher Smith , Andrew Morton , "Timothy D. Witham" , Subject: Re: X15 alpha release: as fast as TUX but in user space In-Reply-To: <3AEDBEB8.449D88C3@chromium.com> Message-ID: X-comment: visit http://arctic.org/~dean/legal for information regarding copyright and disclaimer. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 30 Apr 2001, Fabio Riccardi wrote: > Ok I fixed it, the header date timestamp is updated with every request. > > Performance doesn't seem to have suffered significantly (less than 1%). rad! > BTW: Don't call me slime, I wasn't trying to cheat, I just didn't know that > the date stamp was required to be really up-to-date. sorry, i meant to put a smily on there :) On Sun, 29 Apr 2001, David S. Miller wrote: > If you do the TCP_CORK thing, what you end up with is a scatter gather > entry in the SKB for the header bits, then the page cache segments. so then the NIC would be sent a 3 entry gather list -- 1 entry for TCP/IP headers, 1 for HTTP headers, and 1 for the initial page cache segment? are there any NICs which take only 2 entry lists? (boo hiss and curses on such things if they exist!) -dean - 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/