GSoC: Add SMT/HT awareness to DragonFlyBSD scheduler
Mihai Carabas
mihai.carabas at gmail.com
Tue Jun 26 07:24:13 PDT 2012
--14dae93407ed5199c204c360daff
Content-Type: text/plain; charset=ISO-8859-1
Hello,
Last week I added a feature to be able to simulate a CPU topology within a
vkernel [1] (the lbits and cbits options). Also I had made tests on other
platforms (thanks Alex H. for running the tests) [2][3].
[1] root at dbsd_64:/var/vkernel# ./boot/kernel/kernel -h
Usage: ./boot/kernel/kernel [-hsUv] [-c file] [-e name=value:name=value:...]
[-i file] [-I interface[:address1[:address2][/netmask]]] [-l
cpulock]
[-m size] [-n numcpus[:lbits[:cbits]]]
[-p file] [-r file]
Arguments:
-c Specify a readonly CD-ROM image file to be used by the
kernel.
-e Specify an environment to be used by the kernel.
-h This list of options.
-i Specify a memory image file to be used by the virtual
kernel.
-I Create a virtual network device.
-l Specify which, if any, real CPUs to lock virtual CPUs to.
-m Specify the amount of memory to be used by the kernel in
bytes.
-n Specify the number of CPUs and the topology you wish to
emulate:
- numcpus - number of cpus
- :lbits - specify the number of bits within APICID(=CPUID)
needed for representing
the logical ID. Controls the number of threads/core
(0bits - 1 thread, 1bit - 2 threads).
- :cbits - specify the number of bits within APICID(=CPUID)
needed for representing
the core ID. Controls the number of core/package (0bits -
1 core, 1bit - 2 cores).
[2] http://bugs.dragonflybsd.org/pastes/407
[3] http://bugs.dragonflybsd.org/pastes/408
--14dae93407ed5199c204c360daff
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hello,<div><br></div><div>Last week I added a feature to be able to simulat=
e a CPU topology within a vkernel [1] (the lbits and cbits options). Also I=
had made tests on other platforms (thanks Alex H. for running the tests) [=
2][3].</div>
<div><div><br></div><div><br></div><div>[1]=A0root at dbsd_64:/var/vkernel# ./=
boot/kernel/kernel -h</div><div>Usage: ./boot/kernel/kernel [-hsUv] [-c fil=
e] [-e name=3Dvalue:name=3Dvalue:...]</div><div>=A0 =A0 =A0 =A0 [-i file] [=
-I interface[:address1[:address2][/netmask]]] [-l cpulock]</div>
<div>=A0 =A0 =A0 =A0 [-m size] [-n numcpus[:lbits[:cbits]]]</div><div>=A0 =
=A0 =A0 =A0 [-p file] [-r file]</div><div><br></div><div>Arguments:</div><d=
iv>=A0 =A0 =A0 =A0 -c =A0 =A0 =A0Specify a readonly CD-ROM image file to be=
used by the kernel.</div><div>
=A0 =A0 =A0 =A0 -e =A0 =A0 =A0Specify an environment to be used by the kern=
el.</div><div>=A0 =A0 =A0 =A0 -h =A0 =A0 =A0This list of options.</div><div=
>=A0 =A0 =A0 =A0 -i =A0 =A0 =A0Specify a memory image file to be used by th=
e virtual kernel.</div><div>=A0 =A0 =A0 =A0 -I =A0 =A0 =A0Create a virtual =
network device.</div>
<div>=A0 =A0 =A0 =A0 -l =A0 =A0 =A0Specify which, if any, real CPUs to lock=
virtual CPUs to.</div><div>=A0 =A0 =A0 =A0 -m =A0 =A0 =A0Specify the amoun=
t of memory to be used by the kernel in bytes.</div><div>=A0 =A0 =A0 =A0 -n=
=A0 =A0 =A0Specify the number of CPUs and the topology you wish to emulate=
:</div>
<div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 - numcpus - number of cpus</div><div>=
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 - :lbits - specify the number of bits withi=
n APICID(=3DCPUID) needed for representing</div><div>=A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 the logical ID. Controls the number of threads/core (0bits =
- 1 thread, 1bit - 2 threads).</div>
<div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 - :cbits - specify the number of bits =
within APICID(=3DCPUID) needed for representing</div><div>=A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 the core ID. Controls the number of core/package (0bits=
- 1 core, 1bit - 2 cores).</div>
<div><br></div><br><div class=3D"gmail_quote">[2]=A0<a href=3D"http://bugs.=
dragonflybsd.org/pastes/407">http://bugs.dragonflybsd.org/pastes/407</a></d=
iv></div><div class=3D"gmail_quote">[3]=A0<a href=3D"http://bugs.dragonflyb=
sd.org/pastes/408">http://bugs.dragonflybsd.org/pastes/408</a></div>
--14dae93407ed5199c204c360daff--
More information about the Kernel
mailing list