Date: Tue, 28 Sep 2010 19:19:28 +0100 From: "Robert N. M. Watson" <rwatson@FreeBSD.org> To: Sean Bruno <seanbru@yahoo-inc.com> Cc: "sbruno@freebsd.org" <sbruno@FreeBSD.org>, "freebsd-current@FreeBSD.org" <freebsd-current@FreeBSD.org>, Joshua Neal <jdneal@gmail.com>, John Baldwin <jhb@FreeBSD.org> Subject: Re: MAXCPU preparations Message-ID: <10297FDD-3949-4ED1-88C8-D5C16E0F2069@FreeBSD.org> In-Reply-To: <1285692311.2454.11.camel@home-yahoo> References: <1285601161.7245.7.camel@home-yahoo> <1285604516.7245.16.camel@home-yahoo> <alpine.BSF.2.00.1009272210040.69239@fledge.watson.org> <201009271738.19497.jhb@freebsd.org> <alpine.BSF.2.00.1009272240340.69239@fledge.watson.org> <AANLkTik0Eq2w565cgszvXK4kgDo08%2B28iPkk3CsU-LqC@mail.gmail.com> <alpine.BSF.2.00.1009280846490.69239@fledge.watson.org> <1285692311.2454.11.camel@home-yahoo>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28 Sep 2010, at 17:45, Sean Bruno wrote: > Working on a dynamic version today. I'll spam it over to you for = review > later. =20 >=20 > I'm moving the percpu struct definitions outside of struct = memory_type, > allocating quantity kern.smp.maxcpus, removing the boundary checks = based > on MEMSTAT_MAXCPU and then removing MEMSTAT_MAXCPU all together. Sounds like the right answer. Make sure to also keep the adapt the use = of maxcpus from crashdumps so that we can also size the data structure = when analyzing cores (or /dev/kmem or firewire). Robert=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10297FDD-3949-4ED1-88C8-D5C16E0F2069>