lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 6 Aug 2007 14:48:01 -0700
From:	"Mitchell Erblich" <erblichs@...thlink.net>
To:	"Rene Herman" <rene.herman@...il.com>
Cc:	<linux-kernel@...r.kernel.org>, "Ingo Molnar" <mingo@...e.hu>,
	"\"T. J. Brumfield\"" <enderandrew@...il.com>
Subject: Re: about modularization

Rene,

    Of the uni-processor systems currently that can run Linux, I would not
    doubt if  99.9999% percent are uni-cores. It will be probably
    3-5 years minimum before the multi-core processors will have any
    decent percentage of systems.

    And I am not suggesting not supporting them. I am only suggesting
   is wrt the schedular, bring the system up with a default schedular,
   and then load additional functionality based on the hardware/software
    requirements of the system.

    Thus, the fallout MIGHT be a uni-processor CFS that would not migrate
    tasks between multiple CPUs and as additional processors are brought
    online, migration could be enabled, and gang type scheduling,  whatever
    could be then used.


    IMO, if their is a fault (because of heat, etc) the user would rather
bring
    up the system in a degraded mode. Same reason applies to...
    boot -s..

    Mitchell Erblich
------------------------------


Rene Herman wrote:
>
> On 08/06/2007 10:20 PM, Mitchell Erblich wrote:
>
> >     Thus, a hybrid schedular approach could be taken
> >     that would default to a single uni-processor schedular
>
> What a brilliant idea in a world where buying a non multi core CPU is
> getting to be only somewhat easier than a non SMT one...
>
> Rene.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ