L4linux: cpu and core [comprehension question]
adam at os.inf.tu-dresden.de
Mon Apr 28 00:43:20 CEST 2014
On Fri Apr 25, 2014 at 11:01:24 +0900, Irvanda Kurniadi wrote:
> On Fri, Apr 25, 2014 at 6:40 AM, Adam Lackorzynski <
> adam at os.inf.tu-dresden.de> wrote:
> > On Thu Apr 24, 2014 at 16:47:59 +0900, Irvanda Kurniadi wrote:
> > > I am a little bit confused about the term of cpu and core in l4linux. I
> > > have a system with 8 processor intel xeon E5606 with 4 cores in each cpu.
> > According to the Internet, an E5606 is a quadcore CPU without
> > hyperthreading. Do you mean that you have an 8 socket system and thus 32
> > cores?
> > Yes I do, it means 8 sockets.
> > > I'm going to maximize it to become the maximum number of cores in all
> > cpus.
> > > But I am confused in determining the l4x_cpus that what is the term cpu
> > in
> > > here? Is it literally cpu or the number of threads that can be handled in
> > > each core?
> > l4x_cpus describes how many virtual CPU (L4) threads L4Linux shall
> > create. This is purely software and has no relation to Hyperthreads or
> > similar.
> > I run an openmp hello world apps over l4linux. I call the
> > > omp_get_thread_num() and I got 4 threads in the result. Are these 4
> > threads
> > So you L4Linux is running with 4 vCPUs? (See /proc/cpuinfo for example.)
> > OK, I got it. I put 32 in l4x_cpus, then I check it in /proc/cpuinfo. I
> found that there are only 25 vCpus created from vcpu 0 - 24. At the second
> attempt, there are 28 vCpus created. At the third attempt, there are 32
> vCpus created. Then at fourth attempt there are 31 vCpus created. The
> number of vCpu created isn't always shown with the certain number. Is it
> normal? I don't think this is a normal condition.
Fiasco does not wait starting programs on CPU0 until all CPUs are up
(actually it does not know when this is the case). In your case L4Linux
is already booting when other CPUs are still booting up. So waiting a
bit should make all CPUs available to L4Linux.
Adam adam at os.inf.tu-dresden.de
More information about the l4-hackers