From owner-svn-src-head@FreeBSD.ORG Mon Nov 21 05:55:44 2011 Return-Path: Delivered-To: svn-src-head@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C1521065674; Mon, 21 Nov 2011 05:55:44 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id E2AE48FC13; Mon, 21 Nov 2011 05:55:43 +0000 (UTC) Received: from lstewart.caia.swin.edu.au (lstewart.caia.swin.edu.au [136.186.229.95]) by lauren.room52.net (Postfix) with ESMTPSA id 93F8D7E8C8; Mon, 21 Nov 2011 16:39:20 +1100 (EST) Message-ID: <4EC9E408.9000304@freebsd.org> Date: Mon, 21 Nov 2011 16:39:20 +1100 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111006 Thunderbird/7.0.1 MIME-Version: 1.0 To: Ben Kaduk References: <201111210417.pAL4HOdi023556@svn.freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lauren.room52.net Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Julien Ridoux Subject: Re: svn commit: r227778 - head/sys/net X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2011 05:55:44 -0000 On 11/21/11 16:12, Ben Kaduk wrote: > On Sun, Nov 20, 2011 at 11:17 PM, Lawrence Stewart wrote: >> Author: lstewart >> Date: Mon Nov 21 04:17:24 2011 >> New Revision: 227778 >> URL: http://svn.freebsd.org/changeset/base/227778 >> >> Log: >> - When feed-forward clock support is compiled in, change the BPF header to >> contain both a regular timestamp obtained from the system clock and the >> current feed-forward ffcounter value. This enables new possibilities including > > Is it really necessary to make the ABI dependent on a kernel > configuration option? This causes all sorts of headaches if loadable > modules ever want to use that ABI, something that we just ran into > with vm_page_t and friends and had a long thread on -current about. Fair question. Julien, if pcap and other consumers will happily ignore the new ffcount_stamp member in the bpf header, is there any reason to conditionally add the ffcounter into the header struct? Cheers, Lawrence