From: "David S. Miller" <davem@davemloft.net>
To: akpm@osdl.org
Cc: kiran@scalex86.org, rusty@rustcorp.com.au, dipankar@in.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch 0/6] mm: alloc_percpu and bigrefs
Date: Fri, 23 Sep 2005 00:17:29 -0700 (PDT) [thread overview]
Message-ID: <20050923.001729.101033164.davem@davemloft.net> (raw)
In-Reply-To: <20050923001013.28b7f032.akpm@osdl.org>
From: Andrew Morton <akpm@osdl.org>
Date: Fri, 23 Sep 2005 00:10:13 -0700
> Ravikiran G Thirumalai <kiran@scalex86.org> wrote:
> >
> > Hi Andrew,
> > This patchset contains alloc_percpu + bigrefs + bigrefs for netdevice
> > refcount. This patchset improves tbench lo performance by 6% on a 8 way IBM
> > x445.
>
> I think we'd need more comprehensive benchmarks than this before adding
> large amounts of complex core code.
I agree. tbench over loopback is about as far from real life
as it gets.
I'm still against expanding these networking datastructures with
bigrefs just for this stuff. Some people have per-cpu and per-node on
the brain, and it's starting to bloat things up a little bit too much.
next prev parent reply other threads:[~2005-09-23 7:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050923062529.GA4209@localhost.localdomain>
2005-09-23 7:10 ` [patch 0/6] mm: alloc_percpu and bigrefs Andrew Morton
2005-09-23 7:17 ` David S. Miller [this message]
2005-09-23 8:11 ` Rusty Russell
2005-09-23 11:36 ` Dipankar Sarma
2005-09-23 18:48 ` Ravikiran G Thirumalai
2005-09-23 9:03 ` Eric Dumazet
2005-09-23 9:35 ` Eric Dumazet
2005-09-23 18:40 ` Ravikiran G Thirumalai
2005-09-23 18:50 ` David S. Miller
2005-09-23 23:30 ` Ravikiran G Thirumalai
2005-09-23 19:16 ` Christoph Lameter
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=20050923.001729.101033164.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=dipankar@in.ibm.com \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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