Re: Hyperthreading hurts 5.3?

From: Anthony Atkielski (atkielski.anthony_at_wanadoo.fr)
Date: 01/13/05

  • Next message: Static: "login.conf problems"
    Date: Thu, 13 Jan 2005 02:11:27 +0100
    To: freebsd-questions@freebsd.org
    
    

    Scott Bennett writes:

    SB> I notice that the 5.2.1 boot messages refer to the second core as an
    SB> AP, which I'm guessing stands for "attached processor". If that
    SB> guess is correct, then it means that only the first core is able to
    SB> perform certain functions, and the AP core has to get the first core
    SB> to do those things for it when it needs them done.

    AP just stands for "application processor," from what I've seen. My
    impression from snooping in the code and looking elsewhere is that an AP
    is just a processor that is halted during system boot. The processor
    that executes the boot sequence is the bootstrap processor (BSP). Once
    the boot proceeds far enough to allow synchronization of multiple
    processors, the other processors (APs all) are started by the BSP.

    This doesn't necessarily mean that the BSP is special in any other way
    outside of startup or shutdown, and hopefully it is not, as that would
    defeat much of the conceptual purpose behind SMP. I know that on
    operating systems that insist on keeping one processor special for
    certain tasks, the speed of this processor often becomes a bottleneck on
    heavily loaded systems, as it tops out trying to handle all the
    "restricted" stuff for the other processors and itself.

    SB> What Intel claims is essentially that the HT-enabled CPUs allow
    SB> snappier responses in interactive processes when a CPU-bound process
    SB> is running.

    That I can believe. One of the great advantages to a multiple-processor
    system is that it's much less likely to bog down if a process decides to
    hog a processor (unless the process runs multiple threads). I think MP
    is more interesting for its ability to run completely independent
    processes or threads than it is for its ability to run multiple
    threads doing the same thing. Few applications require multiple
    high-speed processors churning through code all at once.

    -- 
    Anthony
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
    

  • Next message: Static: "login.conf problems"

    Relevant Pages

    • Re: Hyperthreading hurts 5.3?
      ... then it means that only the first core is able to ... >is just a processor that is halted during system boot. ... an I/O operation be the one that fielded the interruptupon completion ... >hog a processor (unless the process runs multiple threads). ...
      (freebsd-questions)
    • Re: Next Generation of Language
      ... by consumers. ... The first multicore (in a single socket macs were the intel boxes, ... and multiple cores per die. ... something for an 8, 16, 32 core box to do. ...
      (comp.lang.lisp)
    • Re: Problems booting on Laptop
      ... > I am having a strange problem with Core 1 on my no name laptop. ... > problem as Fedora then booted. ... But now it refuses to boot and seems to ... Fedora GNU/Linux Core 1 on Athlon CPU kernel 2.4.22-1.2149.nptl ...
      (Fedora)
    • Re: "Multicore may be bad for Java" (and how about .NET)
      ... Applicaple to .NET as well? ... Multi core processors will greatly make this type of functionality a much better reality. ... The problem with running multiple exes as you are considering, is that each exe is still dependent upon each other; that is, if one dies in the process, they will all die. ... you can take advantage of multiple cores running in different processes through a separate VM process that is assigned through session management. ...
      (borland.public.delphi.non-technical)
    • Re: Fedora Core 6 Problems
      ... I'm having numerous problems with Fedora Core 6. ... Start mcstrans and numerous ACPI pid 2357 ... acpi=off from the Grub boot menu. ... You can also turn off services you don't need like cpuspeed, mcstrans, ...
      (linux.redhat)