From owner-cvs-src@FreeBSD.ORG Mon Mar 26 08:43:09 2007 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 644DD16A400; Mon, 26 Mar 2007 08:43:09 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 921B713C469; Mon, 26 Mar 2007 08:43:08 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id l2Q8h4Te077423; Mon, 26 Mar 2007 12:43:04 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id l2Q8h3hS077422; Mon, 26 Mar 2007 12:43:03 +0400 (MSD) (envelope-from yar) Date: Mon, 26 Mar 2007 12:43:02 +0400 From: Yar Tikhiy To: Luigi Rizzo Message-ID: <20070326084302.GD60831@comp.chem.msu.su> References: <200703260450.l2Q4o6vs047638@repoman.freebsd.org> <20070325215959.A82215@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070325215959.A82215@xorpc.icir.org> User-Agent: Mutt/1.5.9i Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/net if_edsc.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2007 08:43:09 -0000 On Sun, Mar 25, 2007 at 09:59:59PM -0700, Luigi Rizzo wrote: > On Mon, Mar 26, 2007 at 04:50:06AM +0000, Yar Tikhiy wrote: > > yar 2007-03-26 04:50:06 UTC > > > > FreeBSD src repository > > > > Added files: > > sys/net if_edsc.c > > Log: > > Introduce a new toy interface, edsc(4). It's a discard interface > > imitating an Ethernet device, so vlan(4) and if_bridge(4) can be > > attached to it for testing and benchmarking purposes. Its source > > can be an introduction to the anatomy of a network interface driver > > due to its simplicity as well as to a bunch of comments in it. > > any mfc plans ? Yes, I have a version of the driver for RELENG_6, too. It may be of certain interest to those who want to learn the differences between RELENG_6 and HEAD. I miss my MFC-after: terms badly, so I ceased using the feature because it looked like I was making promises I couldn't keep. -- Yar