From: Dipankar Sarma <dipankar@in.ibm.com>
To: Niels Christiansen <nchr@us.ibm.com>
Cc: kiran@linux.ibm.com, lse-tech@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] [RFC] [PATCH] Scalable Statistics Counters
Date: Fri, 7 Dec 2001 15:40:17 +0530 [thread overview]
Message-ID: <20011207154017.B15810@in.ibm.com> (raw)
In-Reply-To: <OFEDC68CF2.34B05314-ON85256B1B.00355B4C@raleigh.ibm.com>
In-Reply-To: <OFEDC68CF2.34B05314-ON85256B1B.00355B4C@raleigh.ibm.com>; from nchr@us.ibm.com on Fri, Dec 07, 2001 at 04:52:40AM -0500
On Fri, Dec 07, 2001 at 04:52:40AM -0500, Niels Christiansen wrote:
>
> Hello Dikanpar,
> | It should be easy to place the counters in appropriately close
> | memory if linux gets good NUMA APIs built on top of the topology
> | services. If we extend kmem_cache_alloc() to allocate memory
> | in a particular NUMA node, we could simply do this for placing the
> | counters -
> | ...
> | This would put the block of counters corresponding to a CPU in
> | memory local to the NUMA node. If there are more sophisticated
> | APIs available for suitable memory selection, those too can be made
> | use of here.
> |
> | Is this the kind of thing you are looking at ?
>
> I'm no NUMA person so I can't verify your code snippet but if it does
> what you say, yes, that is exactly what I meant: We may have to deal
> with both cache coherence and placement of counters in local memory.
Yes, we will likely need to place the conters in memory closest to
the corresponding CPUs.
I haven't yet started looking at the current NUMA proposals, but
I hope that there will be support for NUMA-aware allocations. The
flexible allocator scheme in our statctr implementation allows
each counter block corresponding to a CPU to be allocated separately
and we can make the locational judgement at that time as indicated
in my hypothetical changes to the statctr code snippet.
Thanks
Dipankar
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
next prev parent reply other threads:[~2001-12-07 10:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 9:52 [Lse-tech] [RFC] [PATCH] Scalable Statistics Counters Niels Christiansen
2001-12-07 10:10 ` Dipankar Sarma [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-09 10:57 Manfred Spraul
2001-12-10 16:32 ` Jack Steiner
2001-12-10 17:00 ` Manfred Spraul
2001-12-08 17:43 Niels Christiansen
2001-12-09 11:46 ` Anton Blanchard
2001-12-06 16:10 Niels Christiansen
2001-12-07 8:54 ` Dipankar Sarma
2001-12-08 22:24 ` Paul Jackson
2001-12-09 3:46 ` Jack Steiner
2001-12-09 4:44 ` Paul Jackson
2001-12-09 17:34 ` Jack Steiner
2001-12-11 23:27 ` Paul Jackson
2001-12-07 11:39 ` Ravikiran G Thirumalai
2001-12-08 13:46 ` Anton Blanchard
2001-12-05 15:02 Niels Christiansen
2001-12-06 12:33 ` Ravikiran G Thirumalai
2001-12-06 13:07 ` Arjan van de Ven
2001-12-06 14:09 ` Ravikiran G Thirumalai
2001-12-06 14:10 ` Arjan van de Ven
2001-12-06 19:35 ` Dipankar Sarma
2001-12-07 21:09 ` Alex Bligh - linux-kernel
2001-12-07 21:16 ` Arjan van de Ven
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=20011207154017.B15810@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=kiran@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=nchr@us.ibm.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 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.