From: Ravikiran G Thirumalai <kiran@in.ibm.com>
To: Niels Christiansen <nchr@us.ibm.com>
Cc: lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Lse-tech] [RFC] [PATCH] Scalable Statistics Counters
Date: Thu, 6 Dec 2001 18:03:53 +0530 [thread overview]
Message-ID: <20011206180353.E20583@in.ibm.com> (raw)
In-Reply-To: <OF29EF801E.F851F18D-ON85256B19.00510775@raleigh.ibm.com>
In-Reply-To: <OF29EF801E.F851F18D-ON85256B19.00510775@raleigh.ibm.com>; from nchr@us.ibm.com on Wed, Dec 05, 2001 at 10:02:33AM -0500
Hi Niels,
On Wed, Dec 05, 2001 at 10:02:33AM -0500, Niels Christiansen wrote:
>
> I'm wondering about the scope of this. My Ethernet adapter with, maybe, 20
> counter fields would have 20 counters allocated for each of my 16
> processors.
> The only way to get the total would be to use statctr_read() to merge them.
> Same for the who knows how many IP counters etc., etc.
Are you concerned with increase in memory used per counter Here? I suppose
that must not be that much of an issue for a 16 processor box....
>
> How many and which counters were converted for the test you refer to?
>
Well, I wrote a simple kernel module which just increments a shared global
counter a million times per processor in parallel, and compared it with
the statctr which would be incremented a million times per processor in
parallel..
> I do like the idea of a uniform access mechanism, though. It is well in
> line
> with my thoughts about an architected interface for topology and
> instrumentation
> so I'll definitely get back to you as I try to collect requirements.
>
> Niels
Hope we can come out with a really cool and acceptable interface..
Kiran
--
Ravikiran G Thirumalai <kiran@in.ibm.com>
Linux Technology Center, IBM Software Labs,
Bangalore.
next prev parent reply other threads:[~2001-12-06 12:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 15:02 [Lse-tech] [RFC] [PATCH] Scalable Statistics Counters Niels Christiansen
2001-12-06 12:33 ` Ravikiran G Thirumalai [this message]
2001-12-06 12:59 ` Keith Owens
2001-12-06 13:07 ` [Lse-tech] " 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
-- strict thread matches above, loose matches on Subject: below --
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-07 9:52 Niels Christiansen
2001-12-07 10:10 ` Dipankar Sarma
2001-12-08 17:43 Niels Christiansen
2001-12-09 11:46 ` Anton Blanchard
2001-12-09 10:57 Manfred Spraul
2001-12-10 16:32 ` Jack Steiner
2001-12-10 17:00 ` Manfred Spraul
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=20011206180353.E20583@in.ibm.com \
--to=kiran@in.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.