public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Jiri Kosina <jkosina@suse.cz>,
	Jeff Mahoney <jeffm@suse.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Tony Luck <tony.luck@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>,
	linux-ia64@vger.kernel.org
Subject: Re: Commit 34d76c41 causes linker errors on ia64 with NR_CPUS=4096
Date: Tue, 20 Oct 2009 16:39:01 +0900	[thread overview]
Message-ID: <4ADD6915.7000909@kernel.org> (raw)
In-Reply-To: <4ADD62AA.8060503@gmail.com>

Eric Dumazet wrote:
> Ingo Molnar a écrit :
>  
>> Still looks like a bug if it causes a breakage (linker error) on IA64, 
>> and if the 'fix' (i'd call it a workaround) causes a (small but nonzero) 
>> performance regression on other architectures.
>>
> 
> True, but this also save some amount of ram for some distro kernels.
> 
> If we keep this static NR_CPUS thing, we might be able to free
> the end of table, for other per_cpu users ?
> 
> if (nr_cpus_ids < NR_CPUS) {
> 	per_cpu_free_static_zone(&update_shares_data[nr_cpus_ids],
> 				 sizeof(long)*(NR_CPUS - nr_cpus_ids));
> }

That's doable but Considering that the users of NR_CPUS are pretty few
(and should be kept that way), I think it would be better to just use
dynamic allocation, which no longer incurs any major performance
difference (the only difference is constant offset vs. pointer in a
variable), for those cases.

Thanks.

-- 
tejun

  reply	other threads:[~2009-10-20  7:38 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 22:28 Commit 34d76c41 causes linker errors on ia64 with NR_CPUS=4096 Jeff Mahoney
2009-10-20  2:02 ` Jiri Kosina
2009-10-20  4:57   ` Jiri Kosina
2009-10-20  5:21     ` Tejun Heo
2009-10-20  5:58       ` Jiri Kosina
2009-10-20  6:12         ` Tejun Heo
2009-10-20  6:14           ` Tejun Heo
2009-10-20  6:27             ` Jiri Kosina
2009-10-20 14:18               ` Jeff Mahoney
2009-10-20 14:49                 ` Jeff Mahoney
2009-10-21  6:11                   ` Ingo Molnar
2009-10-21 15:19                     ` Tejun Heo
2009-10-21 22:11                       ` Luck, Tony
2009-10-22 14:49                         ` Jiri Kosina
2009-10-22 14:53                           ` Jeff Mahoney
2009-10-22 22:24                           ` Luck, Tony
2009-10-23  7:51                             ` Ingo Molnar
2009-10-23 12:30                               ` Jiri Kosina
2009-10-26 16:38                                 ` Jiri Kosina
2009-10-26 20:16                   ` Ingo Molnar
2009-10-27 10:03                     ` Jiri Kosina
2009-10-27 10:52       ` Jiri Kosina
2009-10-20  6:15     ` Ingo Molnar
2009-10-20  6:26       ` Jiri Kosina
2009-10-20  6:35         ` Ingo Molnar
2009-10-20  7:11           ` Eric Dumazet
2009-10-20  7:39             ` Tejun Heo [this message]
2009-10-20  7:12           ` Tejun Heo
2009-10-20  7:17             ` Jiri Kosina
2009-10-20  7:36               ` Tejun Heo
2009-10-20 13:08           ` Jeff Mahoney
2009-10-20 13:43             ` Ingo Molnar
2009-10-20 13:57               ` Tejun Heo
2009-10-20 13:58                 ` Tejun Heo
2009-10-21  6:43                   ` Christoph Lameter
2009-10-20  9:21       ` Peter Zijlstra

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=4ADD6915.7000909@kernel.org \
    --to=tj@kernel.org \
    --cc=eric.dumazet@gmail.com \
    --cc=fenghua.yu@intel.com \
    --cc=jeffm@suse.com \
    --cc=jkosina@suse.cz \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox