From owner-freebsd-net  Sat May 18 10:12:48 2002
Delivered-To: freebsd-net@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0381037B40C; Sat, 18 May 2002 10:12:40 -0700 (PDT)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA14847;
	Sat, 18 May 2002 13:12:39 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g4IHC9S82047;
	Sat, 18 May 2002 13:12:09 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15590.35689.201153.550505@grasshopper.cs.duke.edu>
Date: Sat, 18 May 2002 13:12:09 -0400 (EDT)
To: "Kenneth D. Merry" <ken@kdm.org>
Cc: current@FreeBSD.org, net@FreeBSD.org
Subject: Re: new zero copy sockets patches available
In-Reply-To: <20020517233950.A36169@panzer.kdm.org>
References: <20020517233950.A36169@panzer.kdm.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org


Kenneth D. Merry writes:
 > 
 > I have released a new set of zero copy sockets patches, against -current
 > from today (May 17th, 2002).
 > 
 > The main change is to deal with the vfs_ioopt changes that Alan Cox made in
 > kern_subr.c.  (They conflicted a bit with the zero copy receive code.)
 > 
 > The patches and the FAQ are available here:
 > 
 > http://people.freebsd.org/~ken/zero_copy/
 > 
 > Comments, questions and reviews are all welcome!
 > 

Hi Ken,

I'm glad to see that you're still maintining this!

Assuming the mutex issues get sorted out, what do you think the odds
are of getting this into the tree?  The only possible issue I see is
with the tigon firmware.   Is the firmware you're using of the same
vintage as what's in the tree now?  Does it contain all the same
fixes?

Thanks again for keeping this alive,

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message