I wanted to boot up single cpu to investigate the latency perf issue. It didn't help.
In general, I am guessing at some point, there will be a use for a "numcpus=N" type of config or cmdline option, if for nothing else to do scalability studies. On Sun, Feb 28, 2016 at 5:58 AM, barret rhoden <[email protected]> wrote: > On 2016-02-28 at 5:49 ron minnich wrote: > > If at all possible I'd like to avoid the addition of CONFIG_ > > variables. Is there any way to make this a boot time option? > > In theory, yes. It's only used in one place > > kern/arch/x86/init.c: #ifdef CONFIG_SINGLE_CORE > > Though I'm tempted to just remove it, since I don't understand its > value, rather than put in get_boot_option calls. It's one of those > ancient things from the early days of Akaros (back when that file was > kern/arch/i386/init.c). > > -- > You received this message because you are subscribed to the Google Groups > "Akaros" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Thanks, Kanoj -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
