From: David Rientjes <rientjes@cs.washington.edu>
To: Paul Jackson <pj@sgi.com>
Cc: linux-mm@kvack.org, akpm@osdl.org, nickpiggin@yahoo.com.au,
ak@suse.de, mbligh@google.com, rohitseth@google.com,
menage@google.com, clameter@sgi.com
Subject: Re: [RFC] another way to speed up fake numa node page_alloc
Date: Wed, 4 Oct 2006 15:10:59 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64N.0610041456480.19080@attu2.cs.washington.edu> (raw)
In-Reply-To: <20061004084552.a07025d7.pj@sgi.com>
On Wed, 4 Oct 2006, Paul Jackson wrote:
> Are you trying to tell to me that the reason I can NOT get away with
> u16 is because I CAN get away with u16, but u8 would be better?
>
> This makes no bleeping sense ...
>
> Not to mention that I obviously can NOT get away with u8, as I already
> have 1024 real nodes on some systems.
>
Isn't this the exact behavior that ordered zonelists are supposed to solve
for real NUMA systems? Has there been an _observed_ case where the cost
to scan the zonelists was considered excessive on real NUMA systems? If
not, then this implementation is simply adding more (and unnecessary)
complexity because now there's two strategies for determining the zones to
check on every get_page_from_freelist and one of the major reasons we
order zonelists in the first place is to deal with NUMA.
> Yes - I am trying to generalize whatever code changes we make to
> get_page_from_freelist() to be at least neutral for all arch's, and
> to benefit at least systems with large counts of nodes, real or fake.
>
I was under the impression that there was nothing wrong with the way
current real NUMA systems allocate pages. If not, please point me to the
thread that _specifically_ discusses this with _data_ that shows it's
inefficient. In fact, when this thread started you recommended as little
changes as possible to the code to not interfere with what already works.
I suggest if changes are going to be made to page allocation on fake AND
real NUMA setups that you provide convincing data that it does indeed
improve the efficiency of such an algorithm and thus far the only test I
have seen you solicit is that of the fake case.
> > I would suggest following Magnus Damm's example ...
>
> I don't know what example you mean - please provide a pointer.
>
It was the same example that I posted in the other thread which caused you
to add Magnus to the Cc.
http://marc.theaimsgroup.com/?l=linux-mm&m=113161386520342
If you read the thread this time, you'll notice that Andi Kleen's original
objection to abstracting this generically was because he felt it was a
debugger hack and didn't deserve the attention. But as more and more
discussion has taken place on the viability of using NUMA emulation in
conjunction with cpusets for the purpose of resource management, perhaps
he has relaxed that objection.
David
--
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:[~2006-10-04 22:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 9:14 Paul Jackson
2006-09-26 6:08 ` David Rientjes
2006-09-26 7:06 ` Paul Jackson
2006-09-26 18:17 ` David Rientjes
2006-09-26 19:24 ` Paul Jackson
2006-09-26 19:58 ` David Rientjes
2006-09-26 21:48 ` Paul Jackson
2006-10-02 6:18 ` Paul Jackson
2006-10-02 6:31 ` David Rientjes
2006-10-02 6:48 ` Paul Jackson
2006-10-02 7:05 ` David Rientjes
2006-10-02 8:41 ` Paul Jackson
2006-10-03 18:15 ` Paul Jackson
2006-10-03 19:37 ` David Rientjes
2006-10-04 15:45 ` Paul Jackson
2006-10-04 16:11 ` Christoph Lameter
2006-10-04 22:10 ` David Rientjes [this message]
2006-10-05 2:27 ` Paul Jackson
2006-10-05 2:37 ` David Rientjes
2006-10-05 2:53 ` Paul Jackson
2006-10-05 3:00 ` David Rientjes
2006-10-05 3:26 ` Paul Jackson
2006-10-05 3:49 ` David Rientjes
2006-10-05 4:07 ` Andrew Morton
2006-10-05 4:14 ` Paul Jackson
2006-10-05 4:50 ` David Rientjes
2006-10-05 4:53 ` Paul Jackson
2006-10-11 3:42 ` Paul Jackson
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=Pine.LNX.4.64N.0610041456480.19080@attu2.cs.washington.edu \
--to=rientjes@cs.washington.edu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@google.com \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.com \
--cc=rohitseth@google.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