From owner-cvs-all Sat Mar 30 7:14:38 2002 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (unknown [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id ABBAB37B417; Sat, 30 Mar 2002 07:14:33 -0800 (PST) Received: (from bde@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g2UFCxl86459; Sat, 30 Mar 2002 07:12:59 -0800 (PST) (envelope-from bde) Message-Id: <200203301512.g2UFCxl86459@freefall.freebsd.org> From: Bruce Evans Date: Sat, 30 Mar 2002 07:12:58 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/gnu/ext2fs ext2_vfsops.c src/sys/isofs/cd9660 cd9660_vfsops.c src/sys/ufs/ffs ffs_vfsops.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG bde 2002/03/30 07:12:58 PST Modified files: sys/gnu/ext2fs ext2_vfsops.c sys/isofs/cd9660 cd9660_vfsops.c sys/ufs/ffs ffs_vfsops.c Log: In ffs_mountffs(), set mnt_iosize_max to si_iosize_max unconditionally provided the latter is nonzero. At this point, the former is a fairly arbitrary default value (DFTPHYS), so changing it to any reasonable value specified by the device driver is safe. Using the maximum of these limits broke ffs clustered i/o for devices whose si_iosize_max is < DFLTPHYS. Using the minimum would break device drivers' ability to increase the active limit from DFTLPHYS up to MAXPHYS. Copied the code for this and the associated (unnecessary?) fixup of mp_iosize_max to all other filesystems that use clustering (ext2fs and msdosfs). It was completely missing. PR: 36309 MFC-after: 1 week Revision Changes Path 1.91 +5 -0 src/sys/gnu/ext2fs/ext2_vfsops.c 1.98 +4 -0 src/sys/isofs/cd9660/cd9660_vfsops.c 1.173 +1 -1 src/sys/ufs/ffs/ffs_vfsops.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message