sm-commit AT lists.ibiblio.org
Subject: Source Mage code commit list
List archive
Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62)
- From: Thomas Orgis <thomas-forum AT orgis.org>
- To: sm-commit AT lists.ibiblio.org
- Subject: Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62)
- Date: Sat, 24 Feb 2007 11:18:17 +0100
Am Sat, 24 Feb 2007 11:10:19 +0200
schrieb Juuso Alasuutari <iuso AT sourcemage.org>:
> On Friday 23 February 2007 23:19, Karsten Behrmann wrote:
> <snip>
> > +# CONFIG_SMP is not set
>
> linux-image-2.6.18-4-686. Multi-core CPUs are becoming commonplace and the
> SMP setting apparently causes no harm on single-core systems. But we'd
> still
> need to test this in practice too just to make sure.
quoting menuconfig help:
If you say N here, the kernel will run on single and
multiprocessor
machines, but will use only one CPU of a multiprocessor machine.
If you say Y here, the kernel will run on many, but not
all, singleprocessor machines. On a singleprocessor machine, the
kernel will run faster if you say N
here.
So I'm more for offering both kernels. I don't know which systems are
excluded by "many, but not all", but as long as we distribute an i486 iso
instead of an i565 or i686 one and especiall as long as we ship a 32bit one
(the multicores being mostly x86_64), the primary target of this iso is a
single core 32bit processor - starting at i486 and compatibles (perhaps
emulated in a vm)...
I am used to other isos offering an smp kernel as additional choice. We could
argue for the future if the smp or the non-smp kernel should be the default,
but I really think we should have both.
Producing the two should really not be the problem. Set the few different
config vars, build, run the scripts (initrd), and just include one entry more
for isolinux prompt.
At last, smgl is about choice ...
Thomas.
-
[SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62),
Karsten Behrmann, 02/23/2007
-
Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62),
Juuso Alasuutari, 02/24/2007
-
Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62),
Thomas Orgis, 02/24/2007
- Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62), Juuso Alasuutari, 02/24/2007
-
Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62),
Eric Sandall, 02/24/2007
- Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62), Jeremy Blosser, 02/24/2007
-
Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62),
Thomas Orgis, 02/24/2007
-
Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62),
Ladislav Hagara, 02/24/2007
-
Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62),
Karsten Behrmann, 02/25/2007
- Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62), Ladislav Hagara, 02/25/2007
-
Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62),
Karsten Behrmann, 02/25/2007
-
Re: [SM-Commit] GIT changes to master cauldron by Karsten Behrmann (c8826657025d00ccd780bbf03ac4862b815d4c62),
Juuso Alasuutari, 02/24/2007
Archive powered by MHonArc 2.6.24.