From: quanstro@quanstro.net (erik quanstrom)
Subject: [9fans] cores a go go
Date: Thu, 31 Mar 2011 00:39:10 -0400 [thread overview]
Message-ID: <f8363beadbbae15ba4da1adac805b16e@brasstown.quanstro.net> (raw)
i rerolled the atom cd today with some noticable changes
for mp systems.
1. apic handling has changed. the mp code can now handle
apic ids > 7. this can affect machines with fewer than 8 cores,
especially intel 2xxx-series and xeon 56xx-series processors.
2. the apic code has a hack to find intel ht processors, even
when there is no mp table entry. (as per usual.) you might
see twice as many cores.
3. msi interrupts are now the default. see apic(3).
http://www.quanstro.net/magic/man2html/3/apic
this has been tested on a variety of phenom ii, opteron c32, intel 5[56]xx.
intel core i7, intel atom, and pentium iv systems from 2-24 cores.
but i'd be interested in hearing of any success/failure.
- erik
next reply other threads:[~2011-03-31 4:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 4:39 erik quanstrom [this message]
2011-03-31 14:12 ` David Leimbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f8363beadbbae15ba4da1adac805b16e@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).