Date: Thu, 1 Jun 2006 19:57:41 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: freebsd-current@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: md /tmp and async mounts Message-ID: <20060601235740.GA39491@xor.obsecurity.org> In-Reply-To: <20060601213527.GA53422@gothmog.pc> References: <20060522231437.GC1446@odin.ac.hmc.edu> <20060523133037.GA2908@gothmog.pc> <20060523143013.GA11472@ci0.org> <20060523194106.GA46634@xor.obsecurity.org> <20060524203645.GB13500@gothmog.pc> <20060524203747.GA88742@xor.obsecurity.org> <20060524204617.GA13701@gothmog.pc> <20060601002024.GA1453@gothmog.pc> <20060601210655.GA36389@xor.obsecurity.org> <20060601213527.GA53422@gothmog.pc>
next in thread | previous in thread | raw e-mail | index | archive | help
--XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 02, 2006 at 12:35:27AM +0300, Giorgos Keramidas wrote: > On 2006-06-01 17:06, Kris Kennaway <kris@obsecurity.org> wrote: > > On Thu, Jun 01, 2006 at 03:20:24AM +0300, Giorgos Keramidas wrote: > > > > [diff snipped] > > > > Thanks for the patch. > > > > > This doesn't make 'async' the default for all mdmfs mounts. > > > > > > Making async the default for mdmfs-based filesystems would > > > require a fair bit of changes to mdmfs, which would have to grow > > > mount-option parsing capabilities for the `optarg' of the -o > > > option and make sure that async is always added, unless mdmfs is > > > called explicitly with `noasync' in its -o option. > > > > > > Having said this, if this is considered a change we should make, > > > I can prepare a patch for mdmfs too. > > > > I think it should be the default. I think we should also avoid using > > -M (malloc backing for md) in favour of swap backing because of the > > panic problems - this is too easy to trigger by accident and it makes > > FreeBSD look bad since it looks like a bug. >=20 > Ok, I'll prepare a patch that enables async and disables -M. We should > also document the fact that tmpmfs=3D"YES" and varmfs=3D"YES" in rc.conf = may > require the presence of at least one swap device by default, and point > the users to -M with a warning if they run FreeBSD without a swap device > but still want to use tmpmfs or varmfs :) Actually I thought about this and don't think it's the case. swap backing doesn't use swap unless you have memory pressure, and if you have memory pressure and no swap your system is going to explode regardless. Kris --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEf370Wry0BWjoQKURArXwAKCW25AzcD+8qA5LgpwtRvxDu08qEQCfapOC p0PeNVkwcx3gWUU3gwd9u+8= =cxh0 -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060601235740.GA39491>