From owner-freebsd-current@FreeBSD.ORG Sat Aug 18 21:43:15 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF9F5106564A for ; Sat, 18 Aug 2012 21:43:14 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id C5AE68FC0A for ; Sat, 18 Aug 2012 21:43:14 +0000 (UTC) Received: from [172.16.1.34] (float34.in1.lcl [172.16.1.34]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id q7ILhES5040312 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 18 Aug 2012 14:43:14 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <50300C6D.3030501@feral.com> Date: Sat, 18 Aug 2012 14:43:09 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Poul-Henning Kamp References: <6882.1345325806@critter.freebsd.dk> In-Reply-To: <6882.1345325806@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Sat, 18 Aug 2012 14:43:14 -0700 (PDT) Cc: freebsd-current@freebsd.org Subject: Re: BUFSIZ = 1024, still ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matt Jacob List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2012 21:43:15 -0000 On 8/18/2012 2:36 PM, Poul-Henning Kamp wrote: > In message <50300540.9060906@feral.com>, Matthew Jacob writes: > >> [...] that there might be a measurable >> difference for having to copy 4K (unaligned) than 1K (unaligned) to >> kernel space for disposition. > Actually, as far as I'm aware, the 4K would be page-aligned by > default due to our malloc(3) implementation. > >> Wasn't there just a recent discussion about running 1.x binaries? > 1.x binaries wouldn't notice and wouldn't be able to tell > if BUFSIZ is different in 10.x I wasn't concerned about those specifically- I was just using this as an example of leaving stuff alone. >> If you're going to talk about making a change to defaults, the default >> MAXPHYS and DLFTPHYS have been undersized for years now. > Indeed, but as I understand it, those require device driver changes ? Ah, well 10.X would be an ideal time to find out!