All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Brent Casavant <bcasavan@sgi.com>
Cc: Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/3] NUMA boot hash allocation interleaving
Date: Tue, 14 Dec 2004 22:00:28 +0000	[thread overview]
Message-ID: <50260000.1103061628@flay> (raw)
In-Reply-To: <Pine.SGI.4.61.0412141720420.22462@kzerza.americas.sgi.com>

>> > I originally was a bit worried about the TLB usage, but it doesn't
>> > seem to be a too big issue (hopefully the benchmarks weren't too
>> > micro though)
>> 
>> Well, as long as we stripe on large page boundaries, it should be fine,
>> I'd think. On PPC64, it'll screw the SLB, but ... tough ;-) We can either
>> turn it off, or only do it on things larger than the segment size, and
>> just round-robin the rest, or allocate from node with most free.
> 
> Is there a reasonably easy-to-use existing infrastructure to do this?
> I didn't find anything in my examination of vmalloc itself, so I gave
> up on the idea.

Not that I know of. But (without looking at it), it wouldn't seem 
desperately hard to implement (some argument or flag to vmalloc, or vmalloc_largepage) or something.

> And just to clarify, are you saying you want to see this before inclusion
> in mainline kernels, or that it would be nice to have but not necessary?

I'd say it's a nice to have, rather than necessary, as long as it's not
forced upon people. Maybe a config option that's on by default on ia64
or something. Causing yourself TLB problems is much more acceptable than
causing it for others ;-)

M.


WARNING: multiple messages have this Message-ID (diff)
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Brent Casavant <bcasavan@sgi.com>
Cc: Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/3] NUMA boot hash allocation interleaving
Date: Tue, 14 Dec 2004 14:00:28 -0800	[thread overview]
Message-ID: <50260000.1103061628@flay> (raw)
In-Reply-To: <Pine.SGI.4.61.0412141720420.22462@kzerza.americas.sgi.com>

>> > I originally was a bit worried about the TLB usage, but it doesn't
>> > seem to be a too big issue (hopefully the benchmarks weren't too
>> > micro though)
>> 
>> Well, as long as we stripe on large page boundaries, it should be fine,
>> I'd think. On PPC64, it'll screw the SLB, but ... tough ;-) We can either
>> turn it off, or only do it on things larger than the segment size, and
>> just round-robin the rest, or allocate from node with most free.
> 
> Is there a reasonably easy-to-use existing infrastructure to do this?
> I didn't find anything in my examination of vmalloc itself, so I gave
> up on the idea.

Not that I know of. But (without looking at it), it wouldn't seem 
desperately hard to implement (some argument or flag to vmalloc, or vmalloc_largepage) or something.

> And just to clarify, are you saying you want to see this before inclusion
> in mainline kernels, or that it would be nice to have but not necessary?

I'd say it's a nice to have, rather than necessary, as long as it's not
forced upon people. Maybe a config option that's on by default on ia64
or something. Causing yourself TLB problems is much more acceptable than
causing it for others ;-)

M.


WARNING: multiple messages have this Message-ID (diff)
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Brent Casavant <bcasavan@sgi.com>
Cc: Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/3] NUMA boot hash allocation interleaving
Date: Tue, 14 Dec 2004 14:00:28 -0800	[thread overview]
Message-ID: <50260000.1103061628@flay> (raw)
In-Reply-To: <Pine.SGI.4.61.0412141720420.22462@kzerza.americas.sgi.com>

>> > I originally was a bit worried about the TLB usage, but it doesn't
>> > seem to be a too big issue (hopefully the benchmarks weren't too
>> > micro though)
>> 
>> Well, as long as we stripe on large page boundaries, it should be fine,
>> I'd think. On PPC64, it'll screw the SLB, but ... tough ;-) We can either
>> turn it off, or only do it on things larger than the segment size, and
>> just round-robin the rest, or allocate from node with most free.
> 
> Is there a reasonably easy-to-use existing infrastructure to do this?
> I didn't find anything in my examination of vmalloc itself, so I gave
> up on the idea.

Not that I know of. But (without looking at it), it wouldn't seem 
desperately hard to implement (some argument or flag to vmalloc, or vmalloc_largepage) or something.

> And just to clarify, are you saying you want to see this before inclusion
> in mainline kernels, or that it would be nice to have but not necessary?

I'd say it's a nice to have, rather than necessary, as long as it's not
forced upon people. Maybe a config option that's on by default on ia64
or something. Causing yourself TLB problems is much more acceptable than
causing it for others ;-)

M.

--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-12-14 22:00 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 17:53 [PATCH 0/3] NUMA boot hash allocation interleaving Brent Casavant
2004-12-14 17:53 ` Brent Casavant
2004-12-14 17:53 ` Brent Casavant
2004-12-14 18:32 ` Luck, Tony
2004-12-14 18:32   ` Luck, Tony
2004-12-14 18:32   ` Luck, Tony
2004-12-15  0:28   ` Hiroyuki KAMEZAWA
2004-12-15  0:28     ` Hiroyuki KAMEZAWA
2004-12-15  0:28     ` Hiroyuki KAMEZAWA
2004-12-14 18:59 ` Martin J. Bligh
2004-12-14 18:59   ` Martin J. Bligh
2004-12-14 18:59   ` Martin J. Bligh
2004-12-14 19:13   ` Andi Kleen
2004-12-14 19:13     ` Andi Kleen
2004-12-14 19:13     ` Andi Kleen
2004-12-14 19:48     ` Brent Casavant
2004-12-14 19:48       ` Brent Casavant
2004-12-14 19:48       ` Brent Casavant
2004-12-14 20:08     ` Martin J. Bligh
2004-12-14 20:08       ` Martin J. Bligh
2004-12-14 20:08       ` Martin J. Bligh
2004-12-14 23:24       ` Brent Casavant
2004-12-14 23:24         ` Brent Casavant
2004-12-14 23:24         ` Brent Casavant
2004-12-14 22:00         ` Martin J. Bligh [this message]
2004-12-14 22:00           ` Martin J. Bligh
2004-12-14 22:00           ` Martin J. Bligh
2004-12-15  4:58           ` Andi Kleen
2004-12-15  4:58             ` Andi Kleen
2004-12-15  4:58             ` Andi Kleen
2004-12-15 14:47             ` Anton Blanchard
2004-12-15 14:47               ` Anton Blanchard
2004-12-15 14:47               ` Anton Blanchard
2004-12-15 23:37               ` Brent Casavant
2004-12-15 23:37                 ` Brent Casavant
2004-12-15 23:37                 ` Brent Casavant
2004-12-16  5:02               ` Andi Kleen
2004-12-16  5:02                 ` Andi Kleen
2004-12-16  5:02                 ` Andi Kleen
2004-12-16  5:13                 ` Anton Blanchard
2004-12-16 14:18                   ` Jose R. Santos
2004-12-16 14:18                     ` Jose R. Santos
2004-12-16 14:18                     ` Jose R. Santos
2004-12-20 16:56                     ` Jose R. Santos
2004-12-20 16:56                       ` Jose R. Santos
2004-12-20 16:56                       ` Jose R. Santos
2004-12-21 11:46                       ` Anton Blanchard
2004-12-21 11:46                         ` Anton Blanchard
2004-12-21 11:46                         ` Anton Blanchard
2004-12-21 16:23                         ` Brent Casavant
2004-12-21 16:23                           ` Brent Casavant
2004-12-21 16:23                           ` Brent Casavant
2004-12-23  2:19                           ` Jose R. Santos
2004-12-23  2:19                             ` Jose R. Santos
2004-12-23  2:19                             ` Jose R. Santos
2004-12-15  4:08         ` Andi Kleen
2004-12-15  4:08           ` Andi Kleen
2004-12-15  4:08           ` Andi Kleen
2004-12-15  7:14           ` Martin J. Bligh
2004-12-15  7:14             ` Martin J. Bligh
2004-12-15  7:14             ` Martin J. Bligh
2004-12-15  7:17             ` Andi Kleen
2004-12-15  7:17               ` Andi Kleen
2004-12-15  7:17               ` Andi Kleen
2004-12-15 15:08               ` Martin J. Bligh
2004-12-15 15:08                 ` Martin J. Bligh
2004-12-15 15:08                 ` Martin J. Bligh
2004-12-15 18:24               ` Brent Casavant
2004-12-15 18:24                 ` Brent Casavant
2004-12-15 18:24                 ` Brent Casavant
2004-12-15  7:41           ` Eric Dumazet
2004-12-15  7:41             ` Eric Dumazet
2004-12-15  7:41             ` Eric Dumazet
2004-12-15  7:46             ` Andi Kleen
2004-12-15  7:46               ` Andi Kleen
2004-12-15  7:46               ` Andi Kleen
2004-12-15  9:14               ` Andi Kleen
2004-12-15  9:14                 ` Andi Kleen
2004-12-15  9:14                 ` Andi Kleen
2004-12-14 23:24     ` Nick Piggin
2004-12-14 23:24       ` Nick Piggin
2004-12-14 23:24       ` Nick Piggin
2004-12-14 19:30   ` Brent Casavant
2004-12-14 19:30     ` Brent Casavant
2004-12-14 19:30     ` Brent Casavant
2004-12-14 20:10     ` Martin J. Bligh
2004-12-14 20:10       ` Martin J. Bligh
2004-12-14 20:10       ` Martin J. Bligh
2004-12-15 17:25 ` Luck, Tony
2004-12-15 17:25   ` Luck, Tony
2004-12-15 17:25   ` Luck, Tony
  -- strict thread matches above, loose matches on Subject: below --
2004-12-20 23:36 Brent Casavant

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=50260000.1103061628@flay \
    --to=martin.bligh@us.ibm.com \
    --cc=ak@suse.de \
    --cc=bcasavan@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.