* RE: [Lse-tech] [RFC] numa slab for 2.5.41-mm1
@ 2002-10-08 23:29 Luck, Tony
2002-10-08 23:34 ` Martin J. Bligh
2002-10-09 0:50 ` David S. Miller
0 siblings, 2 replies; 3+ messages in thread
From: Luck, Tony @ 2002-10-08 23:29 UTC (permalink / raw)
To: lse-tech
Cc: Kamble, Nitin A, linux-kernel, tomlins, akpm,
'Martin J. Bligh'
Manfred Spraul wrote:
> - is it possible implement ptr_to_nodeid()
> on all archs efficiently? It will happen for every kfree().
The best platform independent way that I came up with was to stash
the node id in the page structure ... the initial patch that Nitin
posted included code for this (and it's all my fault that this
added an extra element to the page structure). I think that you
suggested that slab could overload the use of some existing field
if we wanted to pursue this direction.
If ptr_to_nodeid() is made a platform dependent function, then
there are some platforms that can do this very efficiently (since
the nodeid is embedded in some of the high-order address bits), and
some for which this is complex (e.g. platforms that concatenate
memory from each node).
-Tony
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: [Lse-tech] [RFC] numa slab for 2.5.41-mm1
2002-10-08 23:29 [Lse-tech] [RFC] numa slab for 2.5.41-mm1 Luck, Tony
@ 2002-10-08 23:34 ` Martin J. Bligh
2002-10-09 0:50 ` David S. Miller
1 sibling, 0 replies; 3+ messages in thread
From: Martin J. Bligh @ 2002-10-08 23:34 UTC (permalink / raw)
To: Luck, Tony, lse-tech; +Cc: Kamble, Nitin A, linux-kernel, tomlins, akpm
>> - is it possible implement ptr_to_nodeid()
>> on all archs efficiently? It will happen for every kfree().
>
> The best platform independent way that I came up with was to stash
> the node id in the page structure ... the initial patch that Nitin
> posted included code for this (and it's all my fault that this
> added an extra element to the page structure). I think that you
> suggested that slab could overload the use of some existing field
> if we wanted to pursue this direction.
>
> If ptr_to_nodeid() is made a platform dependent function, then
I think that's really the key .... the platforms should just make this
efficient, it's not something for the slab to worry about specifically.
Those of us that have virtual address space to burn can stick it in
struct page, whereas other people (eg me) might have to find some
other way to do it .... but that's the arch people's problem ;-)
> there are some platforms that can do this very efficiently (since
> the nodeid is embedded in some of the high-order address bits), and
> some for which this is complex (e.g. platforms that concatenate
> memory from each node).
M.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Lse-tech] [RFC] numa slab for 2.5.41-mm1
2002-10-08 23:29 [Lse-tech] [RFC] numa slab for 2.5.41-mm1 Luck, Tony
2002-10-08 23:34 ` Martin J. Bligh
@ 2002-10-09 0:50 ` David S. Miller
1 sibling, 0 replies; 3+ messages in thread
From: David S. Miller @ 2002-10-09 0:50 UTC (permalink / raw)
To: tony.luck; +Cc: lse-tech, nitin.a.kamble, linux-kernel, tomlins, akpm, mbligh
From: "Luck, Tony" <tony.luck@intel.com>
Date: Tue, 8 Oct 2002 16:29:45 -0700
If ptr_to_nodeid() is made a platform dependent function, then
there are some platforms that can do this very efficiently (since
the nodeid is embedded in some of the high-order address bits), and
some for which this is complex (e.g. platforms that concatenate
memory from each node).
I suggest to do it like this, provide the portable version unless some
"HAVE_ARCH_PTR_TO_NODEID" CCP macro is defined in which case the
architecture can make the "address bits" optimization or similar.
The is how we usually handle such things.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-10-09 0:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-10-08 23:29 [Lse-tech] [RFC] numa slab for 2.5.41-mm1 Luck, Tony
2002-10-08 23:34 ` Martin J. Bligh
2002-10-09 0:50 ` David S. Miller
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.