From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Dave Hansen <haveblue@us.ibm.com>
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:14:21 -0700 [thread overview]
Message-ID: <20050728181421.GA3842@localhost.localdomain> (raw)
In-Reply-To: <1122571226.23386.44.camel@localhost>
On Thu, Jul 28, 2005 at 10:20:26AM -0700, Dave Hansen wrote:
> On Wed, 2005-07-27 at 18:31 -0700, Ravikiran G Thirumalai wrote:
> > On Wed, Jul 27, 2005 at 06:17:24PM -0700, Andrew Morton wrote:
> > > Ravikiran G Thirumalai <kiran@scalex86.org> wrote:
> > > >
> > Yes, it does cause a crash.
>
> I don't know of any NUMA x86 sub-arches that have nodes which are
> aligned on any less than 2MB. Is this an architecture that's supported
> in the tree, today?
SRAT need not guarantee any alignment at all in the memory affinity
structure (the address in 64-bit byte address). And yes, there are x86-numa
machines that run the latest kernel tree and face this problem.
Thanks,
Kiran
WARNING: multiple messages have this Message-ID (diff)
From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Dave Hansen <haveblue@us.ibm.com>
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:14:21 -0700 [thread overview]
Message-ID: <20050728181421.GA3842@localhost.localdomain> (raw)
In-Reply-To: <1122571226.23386.44.camel@localhost>
On Thu, Jul 28, 2005 at 10:20:26AM -0700, Dave Hansen wrote:
> On Wed, 2005-07-27 at 18:31 -0700, Ravikiran G Thirumalai wrote:
> > On Wed, Jul 27, 2005 at 06:17:24PM -0700, Andrew Morton wrote:
> > > Ravikiran G Thirumalai <kiran@scalex86.org> wrote:
> > > >
> > Yes, it does cause a crash.
>
> I don't know of any NUMA x86 sub-arches that have nodes which are
> aligned on any less than 2MB. Is this an architecture that's supported
> in the tree, today?
SRAT need not guarantee any alignment at all in the memory affinity
structure (the address in 64-bit byte address). And yes, there are x86-numa
machines that run the latest kernel tree and face this problem.
Thanks,
Kiran
--
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:16 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 [this message]
2005-07-28 18:14 ` Ravikiran G Thirumalai
2005-07-28 18:25 ` Dave Hansen
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=20050728181421.GA3842@localhost.localdomain \
--to=kiran@scalex86.org \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--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.