From owner-freebsd-current@FreeBSD.ORG Tue Feb 26 22:35:05 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C6521065672 for ; Tue, 26 Feb 2008 22:35:05 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outP.internet-mail-service.net (outP.internet-mail-service.net [216.240.47.239]) by mx1.freebsd.org (Postfix) with ESMTP id 4C6D313C469 for ; Tue, 26 Feb 2008 22:35:05 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Tue, 26 Feb 2008 14:35:04 -0800 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id E8377127366; Tue, 26 Feb 2008 14:35:03 -0800 (PST) Message-ID: <47C49426.7090104@elischer.org> Date: Tue, 26 Feb 2008 14:35:18 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Peter Jeremy References: <47C39948.3080907@elischer.org> <20080226051346.GA65258@lor.one-eyed-alien.net> <47C3A43C.7090308@elischer.org> <20080226190002.GT83599@server.vk2pj.dyndns.org> In-Reply-To: <20080226190002.GT83599@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marko Zec , Brooks Davis , Marko Zec , FreeBSD Current , Marko Zec Subject: Re: warning of pending commit attempt. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2008 22:35:05 -0000 Peter Jeremy wrote: > Overall, vimage sounds very useful. Are there changes to public > kernel interfaces? (ie could it potentially be MFCd) potentially it could.. in the "compiled out" mode (i.e. you decide to not compile vimage in your kernel) the public kernel interfaces are unchanged. At least that is the aim. > > On Mon, Feb 25, 2008 at 09:31:40PM -0800, Julian Elischer wrote: >>>> The current version referred to in the code is implemented in >>>> a manner that allows it to be COMPILED OUT. > > Since even things like INET and INET6 are "compiled in" rather than > "compiled out" on request, why is vimage defaulting to "compiled in" > by default? eh? After importing, it would be compiled out by default. as in, you'd only get it if you ask for it.. > >> No. There are some minor reorganisations of where some variables are, and >> some minor changes but they are pretty easy to confirm as being >> "functionally equivalent". Macros are used to do a lot but there are some >> places where it was not possible to hide it behind a macro, so small >> re-orgs were required.. they really are small in comparison to >> the whole work though, and as I said. quite "provable". > > How much will impact on the ease with which networking stack changes > can be MFCd back to 7.x? minimal change.. In the worst case we could define the vimage macros in 7.0 and make then do the right thing. (if you needed no diffs at all). > >> I say the next few weeks because we need it to happen NOW and >> not "just before 8.0" > > Agreed but I can understand Brook's reluctance to have yet another > roto-tilling of the network stack whilst there still appear to be > a few issues remaining from the last roto-tilling. IMHO, it would > be reasonable to get input from re@ as to whether they would like > the stack left alone for a while to simplify the resolution of any > issues that may crop up once 7.0 is released. I agree that we need to wait for 7.0 but 7 and 8 are already diverging, and the whole point of the 7 branch is to isolate 7 from -current. >