From owner-freebsd-net@freebsd.org Fri Oct 2 10:08:08 2015 Return-Path: Delivered-To: freebsd-net@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 C9270A0E1FA; Fri, 2 Oct 2015 10:08:08 +0000 (UTC) (envelope-from kp@vega.codepro.be) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95FF41825; Fri, 2 Oct 2015 10:08:08 +0000 (UTC) (envelope-from kp@vega.codepro.be) Received: from vega.codepro.be (unknown [172.16.1.3]) by venus.codepro.be (Postfix) with ESMTP id CF743B40F; Fri, 2 Oct 2015 12:08:05 +0200 (CEST) Received: by vega.codepro.be (Postfix, from userid 1001) id C8174FE9F; Fri, 2 Oct 2015 12:08:05 +0200 (CEST) Date: Fri, 2 Oct 2015 12:08:05 +0200 From: Kristof Provost To: freebsd-pf@freebsd.org, freebsd-net@freebsd.org Subject: pf+TSO patch Message-ID: <20151002100805.GL3433@vega.codepro.be> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Checked-By-NSA: Probably User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2015 10:08:08 -0000 Hi, I've found a little time to look at the pf TSO issue (which made pf unusable on Xen VMs, like Amazon EC2). I've posted the patch here: https://reviews.freebsd.org/D3779 It still needs a bit more testing, but so far it looks good. I'd be very grateful for any brave souls who want to give this a try. This work was very kindly sponsored by RootBSD (rootbsd.net). Regards, Kristof