From: Paul Jackson <pj@sgi.com>
To: David Rientjes <rientjes@cs.washington.edu>
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 08:45:52 -0700 [thread overview]
Message-ID: <20061004084552.a07025d7.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0610031231270.4919@attu3.cs.washington.edu>
David responding to pj:
> > I'm still curious as to why I can't get away with an unsigned short there.
> >
>
> Because it's unnecessary. On my 4G machine with numa=fake=256, each of
> these node_id arrays is going to be 1.5K. You could get away with the
> exact same behavior with using a u8 or unsigned char.
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.
> If you are going to abstract this functionality to other architectures or
> even generically
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 would suggest following Magnus Damm's example ...
I don't know what example you mean - please provide a pointer.
> The only thing that is being sped-up with your node_id array
> in each zonelist_faster is moving this calculation from two steps to one
> step; since the mainline implementation today are both inline functions I
> think the improvement is minimal.
No - I'm optimizing cache line misses, not classic algorithmic
complexity or number of function calls. Scanning say 256 zones
with the existing kernel code uses 256 or 512 cache lines, at
one or two per zone. Scanning 256 zones with my zonelist_faster
patch uses however many cache lines it takes to hold 512 consecutive
bytes of memory, which is much fewer.
Hopefully Martin can get us some real numbers.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
--
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 15:45 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 [this message]
2006-10-04 16:11 ` Christoph Lameter
2006-10-04 22:10 ` David Rientjes
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=20061004084552.a07025d7.pj@sgi.com \
--to=pj@sgi.com \
--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=rientjes@cs.washington.edu \
--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