All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Ravikiran G Thirumalai <kiran@in.ibm.com>,
	linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] [RFC] [PATCH] Scalable Statistics Counters
Date: Fri, 7 Dec 2001 01:05:58 +0530	[thread overview]
Message-ID: <20011207010558.A13412@in.ibm.com> (raw)
In-Reply-To: <OF29EF801E.F851F18D-ON85256B19.00510775@raleigh.ibm.com> <20011206180353.E20583@in.ibm.com> <3C0F6D99.8CF24014@redhat.com> <20011206193940.F20583@in.ibm.com> <20011206091015.B16763@devserv.devel.redhat.com>
In-Reply-To: <20011206091015.B16763@devserv.devel.redhat.com>; from arjanv@redhat.com on Thu, Dec 06, 2001 at 09:10:15AM -0500

On Thu, Dec 06, 2001 at 09:10:15AM -0500, Arjan van de Ven wrote:
> On Thu, Dec 06, 2001 at 07:39:40PM +0530, Ravikiran G Thirumalai wrote:
> > But, you cannot deny that there r gonna be a lot of cacheline 
> > invalidations, if you use a global counter.  Using per-cpu versions is
> > definitely going to improve kernel performance.
> 
> there's not that many counters in fact. And if you care about a gige
> counter, just bind the card to a specific CPU and you have ad-hoc per-cpu
> counters...
> 
> The extra cost of getting to them (extra indirection) makes each access 
> more expensive..... in the end it might be a loss.

If it is a low frequency statistics then the expensive access wouldn't 
really matter much, right ? On the other hand, this will likely help 
specially with larger number of CPUs.

> 
> There's several things where per cpu data is useful; low frequency
> statistics is not one of them in my opinion. 

It is quite possible that you are right. What we need to do is
a measurement effort to understand the impact.

Thanks
Dipankar
-- 
Dipankar Sarma  <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.

  reply	other threads:[~2001-12-06 19:31 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
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 [this message]
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=20011207010558.A13412@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=arjanv@redhat.com \
    --cc=kiran@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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.