From: Elad Lahav <elahav@uwaterloo.ca>
To: sparclinux@vger.kernel.org
Subject: Re: Processor IDs on the Niagara
Date: Mon, 15 Sep 2008 21:26:38 +0000 [thread overview]
Message-ID: <48CED30E.3050504@uwaterloo.ca> (raw)
In-Reply-To: <48CADADA.7050604@uwaterloo.ca>
Sorry to be nagging about this...
Maybe I should have provided some motivation in the first place:
Knowing the processor topology may be of importance to a certain class of programmes.
Specifically, I/O-intensive applications (such as a web server), may want to ensure that
interrupts are serviced close to the process/thread executing the service. I have run some
tests that show that servicing interrupts on a different physical package than the one
responsible for the synchronous part of the service can result in very poor performance
(for obvious reasons).
> Niagara T1 is a single "package", with 8 "cores".
Exactly my point. So why isn't there a single physical package ID for all CPUs under
/sys/devices/system/cpu/cpuX/topology/physical_package_id ?
Elad
next prev parent reply other threads:[~2008-09-15 21:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 21:10 Processor IDs on the Niagara Elad Lahav
2008-09-12 21:44 ` David Miller
2008-09-13 0:47 ` Elad Lahav
2008-09-13 0:53 ` Elad Lahav
2008-09-13 1:01 ` David Miller
2008-09-13 1:02 ` David Miller
2008-09-13 1:18 ` David Miller
2008-09-13 1:27 ` Elad Lahav
2008-09-13 1:38 ` David Miller
2008-09-15 21:26 ` Elad Lahav [this message]
2008-09-15 22:09 ` David Miller
2008-09-16 18:47 ` Elad Lahav
2008-09-16 18:48 ` David Miller
2008-09-17 18:45 ` Elad Lahav
2008-10-05 20:47 ` David Miller
2008-10-05 20:57 ` David Miller
2008-10-06 13:15 ` Elad Lahav
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=48CED30E.3050504@uwaterloo.ca \
--to=elahav@uwaterloo.ca \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.