From owner-freebsd-pf@freebsd.org Thu Aug 11 19:23:05 2016 Return-Path: Delivered-To: freebsd-pf@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 DBDF4BB666C for ; Thu, 11 Aug 2016 19:23:05 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "orthanc.ca", Issuer "Let's Encrypt Authority X1" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C514D1898 for ; Thu, 11 Aug 2016 19:23:05 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from [192.168.43.199] ([24.114.41.35]) (authenticated bits=0) by orthanc.ca (8.15.2/8.15.2) with ESMTPSA id u7BJN3CW077227 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 11 Aug 2016 12:23:04 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: multipart/signed; boundary="Apple-Mail=_7DE57CCB-5729-425F-9D26-3125AAFA9398"; protocol="application/pgp-signature"; micalg=pgp-sha256 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Max altq bandwidth 4.26 Gbit X-Pgp-Agent: GPGMail From: Lyndon Nerenberg In-Reply-To: <756d9874-7a2c-e670-2a12-19b810877274@gmail.com> Date: Thu, 11 Aug 2016 12:22:57 -0700 Message-Id: <17ADD883-CDE1-41F8-9F6A-CB5573ACBAE9@orthanc.ca> References: <756d9874-7a2c-e670-2a12-19b810877274@gmail.com> To: freebsd-pf@freebsd.org X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2016 19:23:06 -0000 --Apple-Mail=_7DE57CCB-5729-425F-9D26-3125AAFA9398 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Aug 11, 2016, at 8:15 AM, John Jasen wrote: >=20 > Should FreeBSD fix altq, or follow OpenBSD's lead in this regard? If by this you mean start using OpenBSD's new traffic shaping scheme, = that would mean adopting OpenBSD's current pf(4) implementation. That = debate has been going on for longer than I can remember now. While fixing ALTQ for 64 bits will be something of a pain, it pales in = comparison to a full-on pf(4) replacement. --Apple-Mail=_7DE57CCB-5729-425F-9D26-3125AAFA9398 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJXrNCSAAoJEJCSmizucT9Vc+oP/R9GBB47Cc/r7gS8isu548+B tFoJ0bt/qPElHLwSI+MS43bJkWFEFIPkltFPksv3ohfh1cqx5mFygGrjxOwoqIwq jr8w0Y5WTFGuylA/wDz4Ngsw6ZEOPxgYHlSHR7UfulLz1qDnFDl48EooDJjpPkNk 93HK62NyDyZDgoS0aAuMTVp6V7Y9K47TcBqHmRyzYXF45N1+MoUJPkN1AQXb0GyL QGcUez+Tp6kvrnZ8dyZsyl9aaA1LSOjzJnho3ME8yK6o2DuvYXwTV1kS7t5y5HKw 6aDLaaijQshSHPbR1JVcomgEdvE8sCzbtQZeucXRtYoxJLY517SrfHEXigQWIqvH 8uZtS8CUK0PatxmEEvx5zmw/Rs1zL7lHvY5xeXj64v/NpuHM1bN/PUEXOL7H3OVh qwOvQJki5VHxh2FTnh2wyfAN7irG4NtEstOUYq7Ym0rofFOfuYYmW4JI5yMv0DLY xi1o2LffC4HeF0yL9Wy13Xhek1PwfipMHZ9WwqsIFUUAtNrOry4xZuKIr36wjznP BonDJ0/1sBZdJFKqBFkAAYWzZkG+AW5tS1Ftx5atEJOZdSfenzUUmi2iRdNayuiP fKDpPq3NNrwhHK96NVguSBE9KYNWPiYx14CDd1v6bA+2DBFTugZxM9uAyfu7IW+y dM3kSHC2iH9nQZ3SwJkZ =R228 -----END PGP SIGNATURE----- --Apple-Mail=_7DE57CCB-5729-425F-9D26-3125AAFA9398--