From owner-cvs-all Wed Dec 1 15:39:44 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 2305D14DF7; Wed, 1 Dec 1999 15:39:40 -0800 (PST) (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 PAA09252; Wed, 1 Dec 1999 15:38:53 -0700 (MST) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199912012238.PAA09252@caspian.plutotech.com> X-Mailer: exmh version 2.1.0 09/18/1999 To: Archie Cobbs Cc: gibbs@FreeBSD.org (Justin T. Gibbs), cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern uipc_mbuf.c src/sys/sys mbuf.h In-reply-to: Your message of "Wed, 01 Dec 1999 15:27:45 PST." <199912012327.PAA45003@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Dec 1999 15:38:53 -0700 From: "Justin T. Gibbs" Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk >> How does this work in a 0 copy system? > >Not sure what a '0 copy system' is.. > >Basically all it does is create a completely new mbuf chain containing >the same data as the original. Definitely at least 1 copy :-) There is support in the works for 0 copy transmission and receive for page sized/aligned packets on gig-E cards. In this situation, the kernel doesn't own the data and copying the mbuf chain could be expensive. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message