From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Keiichiro Tokunaga <tokunaga.keiich@jp.fujitsu.com>,
linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net,
lhns-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] [PATCH] Node Hotplug Support
Date: Fri, 07 May 2004 09:16:51 -0700 [thread overview]
Message-ID: <540080000.1083946609@[10.10.2.4]> (raw)
In-Reply-To: <20040508003904.63395ca7.tokunaga.keiich@jp.fujitsu.com>
> ACPI is used to do some hardware manipulation.
> There is no general purpose interface to get hardware information
> and manipulate hardware today, but hardware proprietary interfaces.
> ACPI is one of them, and I decided to use it because:
>
> - Its spec is open.
> - I can use it without any hardware special knowledge:)
You can't base platform-independant Linux code on ACPI, when not all
NUMA boxes will support it. The fact that your particular box may
support it doesn't make it a generally applicable idea ;-)
You need a better abstraction (and preferably one without the massive
complexity whilst you're at it).
M.
next prev parent reply other threads:[~2004-05-07 16:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 15:39 Keiichiro Tokunaga
2004-05-07 15:49 ` Dave Hansen
2004-05-10 1:47 ` Keiichiro Tokunaga
2004-05-10 2:12 ` [Lhns-devel] " Takayoshi Kochi
2004-05-10 11:20 ` Keiichiro Tokunaga
2004-05-10 5:45 ` Dave Hansen
2004-05-13 1:27 ` Keiichiro Tokunaga
2004-05-13 2:04 ` Dave Hansen
2004-05-13 6:35 ` Keiichiro Tokunaga
2004-05-13 6:45 ` Dave Hansen
2004-05-13 6:54 ` [Lhns-devel] " Dave Hansen
2004-05-14 1:13 ` Keiichiro Tokunaga
2004-05-14 1:21 ` Dave Hansen
2004-05-07 16:16 ` Martin J. Bligh [this message]
2004-05-10 2:03 ` [ANNOUNCE] [PATCH] " Keiichiro Tokunaga
[not found] <1TfLX-4M4-9@gated-at.bofh.it>
2004-05-07 19:10 ` Andi Kleen
2004-05-08 18:00 ` Ingo Oeser
2004-05-10 2:17 ` Keiichiro Tokunaga
2004-05-10 19:54 ` Andi Kleen
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='540080000.1083946609@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=lhns-devel@lists.sourceforge.net \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tokunaga.keiich@jp.fujitsu.com \
/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
all inboxes | Powered by JetHome®