Date: Thu, 17 Sep 2015 22:30:15 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: John Baldwin <jhb@freebsd.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r287934 - head/sys/boot/efi/loader Message-ID: <ECBDF384-46DC-4E3C-902F-5D4EEFC22EA8@lists.zabbadoz.net> In-Reply-To: <5683583.PWsk0G3i3G@ralph.baldwin.cx> References: <201509172036.t8HKalKU088025@repo.freebsd.org> <5683583.PWsk0G3i3G@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 17 Sep 2015, at 20:43 , John Baldwin <jhb@freebsd.org> wrote: > > On Thursday, September 17, 2015 08:36:47 PM John Baldwin wrote: >> Author: jhb >> Date: Thu Sep 17 20:36:46 2015 >> New Revision: 287934 >> URL: https://svnweb.freebsd.org/changeset/base/287934 >> >> Log: >> The EFI boot loader allocates a single chunk of contiguous memory to >> hold the kernel, modules, and any other loaded data. This memory block >> is relocated to the kernel's expected location during the transfer of >> control from the loader to the kernel. >> >> The GENERIC kernel on amd64 has recently grown such that a kernel + zfs.ko >> no longer fits in the default staging size. Bump the default size from >> 32MB to 48MB to provide more breathing room. > > I believe that this should work fine for any system with 64MB of RAM. One > downside of the static size is that the loader fails if it can't allocate > a contiguous staging size (it isn't able to grow the staging area on > demand). how do md_images work in that case?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ECBDF384-46DC-4E3C-902F-5D4EEFC22EA8>