From: Bill Davidsen <davidsen@tmr.com>
To: Justin Banks <justinb@bakbone.com>
Cc: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: FW: Linux question
Date: Fri, 07 Mar 2008 13:43:45 -0500 [thread overview]
Message-ID: <47D18CE1.7050206@tmr.com> (raw)
In-Reply-To: <20080306203841.GA4282@bleen.domain.actdsltmp>
Justin Banks wrote:
> Miller, Mike (OS Dev) wrote
>> Is there a way in to limit the kernel to seeing only the cores on a
>> single processor and ignore all other processor cores (eg. leave
>> them in HALT)?
>
> Can't you just echo 0 into /sys/devices/system/cpu/cpuN/online where the
> /sys/devices/system/cpu/cpuN/topology/physical_package_id isn't the one
> you want to keep online?
>
Here's an interesting question, why isn't there an "online" file for
each CPU?
Example:
posidon:davidsen> l /sys/devices/system/cpu/cpu?
/sys/devices/system/cpu/cpu0:
total 0
drwxr-xr-x 5 root 0 Feb 7 12:57 cache
drwxr-xr-x 3 root 0 Mar 7 13:28 cpufreq
-r-------- 1 root 4096 Mar 7 13:28 crash_notes
drwxr-xr-x 2 root 0 Mar 7 13:28 microcode
drwxr-xr-x 2 root 0 Mar 7 13:28 topology
/sys/devices/system/cpu/cpu1:
total 0
drwxr-xr-x 5 root 0 Feb 7 12:57 cache
drwxr-xr-x 3 root 0 Mar 7 13:28 cpufreq
-r-------- 1 root 4096 Mar 7 13:28 crash_notes
drwxr-xr-x 2 root 0 Mar 7 13:28 microcode
-rw-r--r-- 1 root 4096 Mar 7 13:28 online
drwxr-xr-x 2 root 0 Mar 7 13:28 topology
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2008-03-07 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 19:33 FW: Linux question Miller, Mike (OS Dev)
2008-03-06 19:51 ` Cyrill Gorcunov
2008-03-06 20:38 ` Justin Banks
2008-03-07 18:43 ` Bill Davidsen [this message]
2008-03-07 19:13 ` Justin Banks
2008-03-07 19:14 ` Andi Kleen
2008-03-08 17:07 ` Bill Davidsen
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=47D18CE1.7050206@tmr.com \
--to=davidsen@tmr.com \
--cc=Mike.Miller@hp.com \
--cc=justinb@bakbone.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox