From owner-freebsd-current@FreeBSD.ORG Sun Mar 21 17:04:01 2010 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 7D2641065673; Sun, 21 Mar 2010 17:04:01 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id D20C58FC1C; Sun, 21 Mar 2010 17:04:00 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id d23so188509fga.13 for ; Sun, 21 Mar 2010 10:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=meK1mei+IjxUsyPxLAGaHWPeu8K/ID5pXFAbI25Lnt0=; b=E5w+64ki2goCY5cMnXr88PjVoJj1GqRddGK3Fk0N8GlvlMIHtTJWwJtI2sYnxH9y+h DtLJhRyvXqUPZPIed6Jr0OtxwZjFkxCBkUAgEJdhuoshfE7NODaZCWcuuEav3i2x4Sx0 hTO3A75NSPcywoYZRTOUGcZQzK4aXasKv+AzE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=Ts/oIeOHaw9ejSXRrQv95SFPfAZ0DHS18EnQHpmqo3XMF0bCqW5MOAE+i+uIIM2Kmq tgrzZBdXoW8ipbiRLL4NjAwDnThHQZhJrAcqi6eU7TSSBl4GKBC5kCwN2QT2/sBYwB4r Hlv/zOk0d6VPcteHzDJdYX62Is6FmGrMJXcoA= Received: by 10.86.22.2 with SMTP id 2mr511612fgv.17.1269191039808; Sun, 21 Mar 2010 10:03:59 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 16sm1041828fxm.8.2010.03.21.10.03.58 (version=SSLv3 cipher=RC4-MD5); Sun, 21 Mar 2010 10:03:59 -0700 (PDT) Sender: Alexander Motin Message-ID: <4BA6517C.3050509@FreeBSD.org> Date: Sun, 21 Mar 2010 19:03:56 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Scott Long References: <4BA4E7A9.3070502@FreeBSD.org> <201003201753.o2KHrH5x003946@apollo.backplane.com> <891E2580-8DE3-4B82-81C4-F2C07735A854@samsco.org> <4BA52179.9030903@FreeBSD.org> <39C5864C-8A6B-4137-8743-D7B9F30F5939@samsco.org> In-Reply-To: <39C5864C-8A6B-4137-8743-D7B9F30F5939@samsco.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current , freebsd-arch@freebsd.org Subject: Re: Increasing MAXPHYS 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: Sun, 21 Mar 2010 17:04:01 -0000 Scott Long wrote: > On Mar 20, 2010, at 1:26 PM, Alexander Motin wrote: >> As you should remember, we have made it in such way, that all unchecked >> drivers keep using DFLTPHYS, which is not going to be changed ever. So >> there is no problem. I would more worry about non-CAM storages and above >> stuff, like some rare GEOM classes. > > And that's why I say that everything needs to be audited. Are there CAM drivers > that default to being silent on cpi->maxio, but still look at DFLTPHYS and MAXPHYS? If some (most of) drivers silent on cpi->maxio - they will be limited by safe level of DFLTPHYS, which should not be changed ever. There should be no problem. > Are there non-CAM drivers that look at MAXPHYS, or that silently assume that > MAXPHYS will never be more than 128k? That is a question. -- Alexander Motin