From: Rusty Russell <rusty@rustcorp.com.au>
To: David Miller <davem@davemloft.net>
Cc: dada1@cosmosbay.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net: make ip_rt_acct a normal percpu var
Date: Thu, 20 Nov 2008 14:52:35 +1030 [thread overview]
Message-ID: <200811201452.35527.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20081119.151754.44649102.davem@davemloft.net>
On Thursday 20 November 2008 09:47:54 David Miller wrote:
> We make a big fuss (rightly) about a few hundred bytes and this sucker
> is FOUR KILOBYTES.
Sure, but this is just trading 4k runtime for 4k static, ie. it's just
unhiding it. That's very different from adding random bloat.
> Really for the time being I'd rather see this converted to a
> num_possible_cpus() sized normal kzalloc() and direct indexing. I
> don't want the networking to bloat up the main kernel image by so
> much.
Nooooooo! :)
First, num_possible_cpus() is the wrong answer (if there are holes in
cpu_possible_map). Second, there's little point having percpu infrastructure
which people avoid. Third, that memory not going to be numa-aware. Fourth,
the dynamic percpu version is fewer instructions (with dynamic percpu
patches).
I've spent an hour trying to implement DEFINE_PER_CPU_ZERO(), but AFAICT it
can't be done (gas rejects "b" as a section attribute) :(
So I've dropped the patch, but I wonder if this 4k of stats should be here at
all.
Thanks,
Rusty.
next prev parent reply other threads:[~2008-11-20 4:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 10:20 [PATCH] net: make ip_rt_acct a normal percpu var Rusty Russell
2008-11-17 22:36 ` Eric Dumazet
2008-11-18 15:38 ` Rusty Russell
2008-11-19 22:20 ` David Miller
2008-11-19 23:13 ` Rusty Russell
2008-11-19 23:17 ` David Miller
2008-11-20 4:22 ` Rusty Russell [this message]
2008-11-19 23:23 ` Eric Dumazet
2008-11-20 0:28 ` Rusty Russell
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=200811201452.35527.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).