Date: Sun, 25 Jan 1998 13:02:16 +0100 From: Andreas Klemm <andreas@klemm.gtn.com> To: "John S. Dyson" <toor@dyson.iquest.net> Cc: Bill Paul <wpaul@FreeBSD.ORG>, dyson@FreeBSD.ORG, committers@hub.freebsd.org Subject: Re: cvs commit: src/sys/i386/i386 machdep.c src/sys/i386/include param.h src/sys/i386/isa wd.c src/sys/kern kern_physio. Message-ID: <19980125130216.61126@klemm.gtn.com> In-Reply-To: <199801242325.SAA09557@dyson.iquest.net>; from John S. Dyson on Sat, Jan 24, 1998 at 06:25:09PM -0500 References: <199801241653.IAA24679@hub.freebsd.org> <199801242325.SAA09557@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 24, 1998 at 06:25:09PM -0500, John S. Dyson wrote: > Bill Paul said: > > > > Ooooo.... does this mean we will finally be free of the 64K limit on > > physio transfers, so that we can use block sizes larger than 64K > > on tape drives? > > > For now, we are limited to 128K (MAXPHYS), but can be tuned upwards > to 256K without grief. I hope to come up with a better solution, > but the tunable will be the same (with the "better" solution, 1MB > will probably be the limit.) If that 32K limit doesn't exist anymore, we could remove the warning message within dump, not to dump with blocksizes larger than 32k, because in the past we were not able to get such a dump restored afterwards. Would be great, if this change could be isolated in a manner, so that it could be merged into stable. So we would be able to read dumps from other architectures (Solaris 2,...) that doesn't have such a limit ... If I remember right, it's not unusual praxis, to dump with 96, 126 and 128 blocks ( <= 64KB) and we currently had <=32 KB. Andreas /// -- Andreas Klemm powered by ,,symmetric multiprocessor FreeBSD''
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980125130216.61126>