public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Jack Steiner <steiner@sgi.com>,
	linux-kernel@vger.kernel.org, Jesse Barnes <jbarnes@sgi.com>
Subject: Re: [patch] increse MAX_NR_MEMBLKS to same as MAX_NUMNODES on NUMA
Date: 20 Jan 2004 05:59:36 -0500	[thread overview]
Message-ID: <yq0d69erilj.fsf@wildopensource.com> (raw)
In-Reply-To: <11450000.1074579922@[10.10.2.4]>

>>>>> "Martin" == Martin J Bligh <mbligh@aracnet.com> writes:

>> On Mon, Jan 19, 2004 at 06:24:52PM -0800, Jesse Barnes wrote:
>>> I think Martin is referring to the memblk_*line() functions and
>>> the fact that memblks are exported via sysfs to userspace.  That
>>> API hasn't proven very useful so far since it's really waiting for
>>> memory hot add/remove.  Of course, we'll still need structures to
>>> support that for the low level arch specific discontig code, so
>>> any patch that killed memblks in sysfs and elsewhere would have to
>>> take that into account...  (In particular, node_memblk[] is filled
>>> out by the ACPI SRAT parsing code and use for discontig init and
>>> physical->node id conversion.)
>>> 
>>> Jesse
>>  OK, that makes sense.

Martin> Could one of you test this patch for me? Probably just a build
Martin> would do fine.

Martin,

Tried it, no go! It conflicts with arch/ia64/mm/numa.c and
arch/ia64/mm,/discontig.c as Jack had suggested.

Cheers,
Jes

  reply	other threads:[~2004-01-20 11:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 13:05 [patch] increse MAX_NR_MEMBLKS to same as MAX_NUMNODES on NUMA Jes Sorensen
2004-01-19 20:08 ` Martin J. Bligh
2004-01-19 22:45   ` Jack Steiner
2004-01-20  2:24     ` Jesse Barnes
2004-01-20  3:12       ` Jack Steiner
2004-01-20  6:25         ` Martin J. Bligh
2004-01-20 10:59           ` Jes Sorensen [this message]
2004-01-20 16:11             ` Martin J. Bligh
2004-01-22 15:24               ` Jes Sorensen
2004-01-23  6:09                 ` Martin J. Bligh
2004-01-20  5:21       ` Martin J. Bligh

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=yq0d69erilj.fsf@wildopensource.com \
    --to=jes@wildopensource.com \
    --cc=jbarnes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=steiner@sgi.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