From: Dave Hansen <haveblue@us.ibm.com>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
shai@scalex86.org
Subject: Re: [patch] mm: Ensure proper alignment for node_remap_start_pfn
Date: Thu, 28 Jul 2005 11:25:22 -0700 [thread overview]
Message-ID: <1122575122.20800.32.camel@localhost> (raw)
In-Reply-To: <20050728181421.GA3842@localhost.localdomain>
On Thu, 2005-07-28 at 11:14 -0700, Ravikiran G Thirumalai wrote:
> SRAT need not guarantee any alignment at all in the memory affinity
> structure (the address in 64-bit byte address)
The Summit machines (the only x86 user of the SRAT) have other hardware
guarantees about alignment, so I guess that's why we've never
encountered it. Are you using the SRAT on non-Summit hardware? That
doesn't seem possible:
arch/i386/Kconfig:
config ACPI_SRAT
bool
default y
depends on NUMA && (X86_SUMMIT || X86_GENERICARCH)
> And yes, there are x86-numa
> machines that run the latest kernel tree and face this problem.
I didn't say "run the latest kernel tree". *In* the latest kernel
tree :)
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
shai@scalex86.org
Subject: Re: [patch] mm: Ensure proper alignment for node_remap_start_pfn
Date: Thu, 28 Jul 2005 11:25:22 -0700 [thread overview]
Message-ID: <1122575122.20800.32.camel@localhost> (raw)
In-Reply-To: <20050728181421.GA3842@localhost.localdomain>
On Thu, 2005-07-28 at 11:14 -0700, Ravikiran G Thirumalai wrote:
> SRAT need not guarantee any alignment at all in the memory affinity
> structure (the address in 64-bit byte address)
The Summit machines (the only x86 user of the SRAT) have other hardware
guarantees about alignment, so I guess that's why we've never
encountered it. Are you using the SRAT on non-Summit hardware? That
doesn't seem possible:
arch/i386/Kconfig:
config ACPI_SRAT
bool
default y
depends on NUMA && (X86_SUMMIT || X86_GENERICARCH)
> And yes, there are x86-numa
> machines that run the latest kernel tree and face this problem.
I didn't say "run the latest kernel tree". *In* the latest kernel
tree :)
-- Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-07-28 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 0:42 [patch] mm: Ensure proper alignment for node_remap_start_pfn Ravikiran G Thirumalai
2005-07-28 0:42 ` Ravikiran G Thirumalai
2005-07-28 1:17 ` Andrew Morton
2005-07-28 1:17 ` Andrew Morton
2005-07-28 1:31 ` Ravikiran G Thirumalai
2005-07-28 1:31 ` Ravikiran G Thirumalai
2005-07-28 17:20 ` Dave Hansen
2005-07-28 17:20 ` Dave Hansen
2005-07-28 18:14 ` Ravikiran G Thirumalai
2005-07-28 18:14 ` Ravikiran G Thirumalai
2005-07-28 18:25 ` Dave Hansen [this message]
2005-07-28 18:25 ` Dave Hansen
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=1122575122.20800.32.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shai@scalex86.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.