From owner-cvs-all Fri Jul 23 10:46:34 1999 Delivered-To: cvs-all@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id CE9C914BF9; Fri, 23 Jul 1999 10:46:30 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id LAA12993; Fri, 23 Jul 1999 11:43:44 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199907231743.LAA12993@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: "Justin T. Gibbs" , cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: cvs commit: src/release/sysinstall tcpip.c In-reply-to: Your message of "Fri, 23 Jul 1999 10:36:08 PDT." <199907231736.KAA03557@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Jul 1999 11:43:44 -0600 From: "Justin T. Gibbs" Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk >> In zero copy applications, the header and the payload are usually placed >> in separate areas. > >Can you elaborate on this a little? We don't support the two being in >a separate allocation unit at the moment, yet I understood the 'fast >forwarding' code was essentially a zero-copy operation. I have not looked at the code Drew Gallatin used for his myrinet work, but here at Pluto, we plan to ship the header information into CPU memory and the payload to another PCI device's memory. I would expect a similar approach to be used for page flipping packet payloads into user space in more conventional zero-copy applications. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message