From: Chris Snook <csnook@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Purpose of numa_node?
Date: Wed, 30 Jan 2008 19:48:13 -0500 [thread overview]
Message-ID: <47A11ACD.1090400@redhat.com> (raw)
While pondering ways to optimize I/O and swapping on large NUMA machines, I
noticed that the numa_node field in struct device isn't actually used anywhere.
We just have a couple dozen lines of code to conditionally create a sysfs file
that will always return -1. Is anyone even working on code to actually use this
field? I think it's a good piece of information to keep track of, so I'm not
suggesting we remove it, but I want to make sure I'm not stepping on toes or
duplicating effort if I try to make it useful.
-- Chris
next reply other threads:[~2008-01-31 0:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 0:48 Chris Snook [this message]
2008-01-31 7:40 ` Purpose of numa_node? Paul Mundt
2008-01-31 9:56 ` Andi Kleen
2008-01-31 13:42 ` Brice Goglin
2008-01-31 21:29 ` Yinghai Lu
2008-01-31 21:35 ` Brice Goglin
2008-01-31 21:42 ` Yinghai Lu
2008-01-31 23:35 ` Yinghai Lu
2008-02-13 18:52 ` Brice Goglin
2008-02-13 21:31 ` Yinghai Lu
2008-02-20 21:55 ` Yinghai Lu
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=47A11ACD.1090400@redhat.com \
--to=csnook@redhat.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 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.