netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: Christoph Lameter <christoph@lameter.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net, shai@scalex86.org, akpm@osdl.org
Subject: Re: [PATCH] dst numa: Avoid dst counter cacheline bouncing
Date: Fri, 24 Jun 2005 12:59:26 +0530	[thread overview]
Message-ID: <20050624072926.GA4804@in.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0506232204320.30382@graphe.net>

On Thu, Jun 23, 2005 at 10:05:09PM -0700, Christoph Lameter wrote:
> On Fri, 24 Jun 2005, Dipankar Sarma wrote:
> 
> > Do we really need to do a distributed reference counter implementation
> > inside dst cache code ? If you are willing to wait for a while,
> > we should have modified Rusty's bigref implementation on top of the 
> > interleaving dynamic per-cpu allocator. We can look at distributed 
> > reference counter for dst refcount then and see how that can be 
> > worked out.
> 
> Is that code available somewhere?

Various places in lkml discussions. Search for discussions on dynamic
per-cpu allocator. Currently Bharata is adding
cpu hotplug awareness in it, but the basic patches work.

BTW, I am not saying that bigref has what you need. What I am trying
to say is that you should see if something like bigref can
be tweaked to use in your case before implementing a new type of
ref counting wholly in dst code.

Thanks
Dipankar

      reply	other threads:[~2005-06-24  7:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.62.0506231953260.28244@graphe.net>
2005-06-24  3:36 ` [PATCH] dst_entry structure use,lastuse and refcnt abstraction David S. Miller
2005-06-24  3:40   ` Christoph Lameter
2005-06-24  3:47     ` David S. Miller
2005-06-24  3:49       ` Christoph Lameter
2005-06-24  3:54         ` David S. Miller
2005-06-24  4:06           ` Christoph Lameter
2005-06-24  4:11             ` David S. Miller
2005-06-24  6:03               ` Christoph Lameter
2005-06-24  6:16                 ` David S. Miller
2005-06-24 10:57               ` [PATCH] bugfix and scalability changes in net/ipv4/route.c Eric Dumazet
2005-06-28 20:14                 ` David S. Miller
     [not found] ` <Pine.LNX.4.62.0506232005030.28244@graphe.net>
2005-06-24  4:58   ` [PATCH] dst numa: Avoid dst counter cacheline bouncing Dipankar Sarma
2005-06-24  5:05     ` Christoph Lameter
2005-06-24  7:29       ` Dipankar Sarma [this message]

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=20050624072926.GA4804@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=christoph@lameter.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shai@scalex86.org \
    /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;
as well as URLs for NNTP newsgroup(s).