From owner-freebsd-ipfw@freebsd.org Thu Aug 4 02:41:45 2016 Return-Path: Delivered-To: freebsd-ipfw@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0794ABADF8A for ; Thu, 4 Aug 2016 02:41:45 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D71171E85; Thu, 4 Aug 2016 02:41:44 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-226-8.lns20.per1.internode.on.net [121.45.226.8]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u742fbOI038968 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 3 Aug 2016 19:41:40 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: IPFW: more "orthogonal? state operations, push into 11? To: lev@FreeBSD.org, Ian Smith References: <9229d4f7-8466-57b0-c954-117736102bd7@FreeBSD.org> <5755F0D3.9060909@FreeBSD.org> <5759DB79.10205@FreeBSD.org> <3d09497c-136c-e217-154c-ba00e6879c6f@freebsd.org> <20160616005016.A15883@sola.nimnet.asn.au> <64d6bdea-fa32-f16f-2fdd-abd33d54d04e@freebsd.org> Cc: "Andrey V. Elsukov" , "Alexander V. Chernikov" , freebsd-ipfw@freebsd.org From: Julian Elischer Message-ID: Date: Thu, 4 Aug 2016 10:41:31 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2016 02:41:45 -0000 On 4/08/2016 12:44 AM, Lev Serebryakov wrote: > On 02.08.2016 09:47, Julian Elischer wrote: > > I don't have rights to commit my changes, and looks like I can not > persuade others that my changes are Ok as-is, with all changes, made on > requests from reviewers. > > Personally, I think, that (1) + (2) is orthogonal to (3) and it should > be different change sets, reviews, etc. And, yes, (3) is great feature > by itself. I think 1 on its own would have good chance.. I'd probably commit it myself :-) save-state as a new keyword, that doesn't do a check-state. 2 is more esoteric. and sort of orthogonal to 1. > >> Do we have any movement on these improvements? >> even similar functionality by different names is ok. >> >> 1/ ability to use keep-state without an implicit check-state. <--- most >> important for me. (store-state)? >> 2/ ability to keep-state without actually doing it <---- less important >> for me. >> 3/ multiple state tables? this was discussed and I thought I saw patches >> but I haven't seen it going in, <-- super luxurious just noticed this IS in...