From: Andrew Morton <akpm@osdl.org>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tvec_bases too large for per-cpu data
Date: Tue, 24 Jan 2006 00:58:06 -0800 [thread overview]
Message-ID: <20060124005806.7e9ab02e.akpm@osdl.org> (raw)
In-Reply-To: <43D5F44C.76F0.0078.0@novell.com>
"Jan Beulich" <JBeulich@novell.com> wrote:
>
> >- The `#ifdef CONFIG_NUMA' in init_timers_cpu() seems to be unnecessary -
> > kmalloc_node() will use kmalloc() if !NUMA.
>
> That is correct, but I wanted the fallback if kmalloc_node() fails (from briefly looking at that code it didn't
> seem like it would do such fallback itself). And calling kmalloc() twice if !NUMA seemed pointless.
I'm sorry, but how were we to know that? Telepathy?
GFP_KERNEL for these size objects is pretty much infallible anyway, so I
wouldn't worry about it. Or allocate all needed storage a little later in
boot with alloc_percpu().
> >- We prefer to do this:
> >
> > if (expr) {
> > ...
> > } else {
> > ...
> > }
> >
> > and not
> >
> > if (expr) {
> > ...
> > }
> > else {
> > ...
> > }
>
> I can change that, too, but I don't see why this gets pointed out again and again when there really
> is no consistency across the entire kernel...
>
We fix these things up when working on incorrectly laid-out code, but we
rarely bother raising a patch just to fix something like that. We'll get
there eventually.
next prev parent reply other threads:[~2006-01-24 8:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 13:11 Jan Beulich
2006-01-21 7:25 ` Andrew Morton
2006-01-23 10:31 ` Jan Beulich
2006-01-23 10:57 ` Andrew Morton
2006-01-24 8:33 ` Jan Beulich
2006-01-24 8:58 ` Andrew Morton [this message]
2006-01-24 14:46 ` [PATCH] [SMP] reduce size of percpudata, and make sure per_cpu(object, not_possible_cpu) cause an invalid memory reference Eric Dumazet
2006-01-24 14:53 ` Andi Kleen
2006-02-01 9:21 ` [PATCH] [SMP] __GENERIC_PER_CPU changes Eric Dumazet
2006-01-30 8:43 ` [PATCH] tvec_bases too large for per-cpu data Jan Beulich
2006-01-31 22:27 ` Andrew Morton
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=20060124005806.7e9ab02e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=JBeulich@novell.com \
--cc=linux-kernel@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
Powered by JetHome