From owner-freebsd-arch@FreeBSD.ORG Mon Jan 7 13:33:07 2008 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E35C316A420 for ; Mon, 7 Jan 2008 13:33:07 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from fallbackmx09.syd.optusnet.com.au (fallbackmx09.syd.optusnet.com.au [211.29.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id 7737913C44B for ; Mon, 7 Jan 2008 13:33:07 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail35.syd.optusnet.com.au (mail35.syd.optusnet.com.au [211.29.133.51]) by fallbackmx09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m079AAQg000300 for ; Mon, 7 Jan 2008 20:10:10 +1100 Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail35.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m079A6Fn030824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jan 2008 20:10:07 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m079A6oq042389; Mon, 7 Jan 2008 20:10:06 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m079A6FI042388; Mon, 7 Jan 2008 20:10:06 +1100 (EST) (envelope-from peter) Date: Mon, 7 Jan 2008 20:10:06 +1100 From: Peter Jeremy To: Robert Watson Message-ID: <20080107091006.GN947@server.vk2pj.dyndns.org> References: <20080106124517.G105@fledge.watson.org> <47811904.4060300@elischer.org> <20080106182340.K105@fledge.watson.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Jl+DbTnyraiZ/loT" Content-Disposition: inline In-Reply-To: <20080106182340.K105@fledge.watson.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: arch@freebsd.org Subject: Re: Network device driver KPI/ABI and TOE X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2008 13:33:08 -0000 --Jl+DbTnyraiZ/loT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 06, 2008 at 06:37:19PM +0000, Robert Watson wrote: >What I'm more concerned about is the new exposure of internal data=20 >structures and algorithms, and a resulting freeze of those data structures= =20 >and algorithms if we were to apply our current ABI/PI policy to the TOE=20 >interfaces. Whilst I doubt TOE will directly affect me in the short term, I would be disappointed if general TCP improvements could not be MFCd because it would change the TOE ABI. I believe that TOE is fairly new and not completely mature feature. Is it possible that further experience with TOE may also lead to changes in the interfaces between TOE and the rest of the kernel, irrespective of the kernel innards? If we do decide to expose a set of interfaces where we do not guarantee the API/ABI, those interfaces need to be clearly documented as such. Solaris (eg) has an "interface stability" section in some of its man pages - maybe we should look at something similar. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --Jl+DbTnyraiZ/loT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHgexu/opHv/APuIcRApYhAKC9EKp/l7oOUQ6e1LsVP6CX7GjrqwCfXQDo bh+YEFsAQ8qIC/roNZECnQE= =HldK -----END PGP SIGNATURE----- --Jl+DbTnyraiZ/loT--