On Sat, May 2, 2015 at 10:25 PM, Adrian Chadd adr...@freebsd.org wrote:
hi,
Hm, should we be upping this limit automatically? Can we get cpu
counts or memory amount early enough in boot to have a hope of
auto-tuning?
64 seems low, 1024 seems high as a default. :)
What is it that's
On 2015-05-16 00:42, Stanislav Sedov wrote:
On May 15, 2015, at 11:30 AM, Michał Stanekm...@semihalf.com wrote:
Hi,
I am experiencing an early failure of UMA on an ARM64 platform with 48
cores enabled. I get a kernel panic during initialization of VM. Here is
the boot log (lines with 'MST:'
Hi all,
Sorry by cross posting, but I want to tell about the
I BSD Day in Seropédica (Rio de Janeiro Brazil)
in yesterday (5/16). It occurred in University UFRRJ
(http://www.ufrrj.br) and the event site is
http://bsdday.fug.com.br.
This event was made to local users, community
of
See https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests2/1040/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
2015-05-13 18:09 GMT+02:00 David Chisnall david.chisn...@cl.cam.ac.uk:
LLVM uses this quite heavily, in a macro that expands to something equivalent
to assert(0 unreachable reached!”) in debug mode and
__builtin_unreachable() in release mode. When you’re debugging, you get
errors if you
