From: Yinghai Lu <yinghai@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irq: optimize init_kstat_irqs/init_copy_kstat_irqs
Date: Sat, 7 Feb 2009 01:01:03 -0800 [thread overview]
Message-ID: <86802c440902070101l5b0ef862ja92e3f31705d9608@mail.gmail.com> (raw)
In-Reply-To: <20090207002610.73ff7e6d.akpm@linux-foundation.org>
On Sat, Feb 7, 2009 at 12:26 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Fri, 06 Feb 2009 23:49:41 -0800 Yinghai Lu <yinghai@kernel.org> wrote:
>
>>
>> Impact: even later type of kstat_irqs is changed
>>
>> simplify and make init_kstat_irqs etc more type prof according to Andrew
>>
>> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>>
>> ---
>> kernel/irq/handle.c | 20 +++++++++++---------
>> kernel/irq/numa_migrate.c | 11 +++--------
>> 2 files changed, 14 insertions(+), 17 deletions(-)
>>
>> Index: linux-2.6/kernel/irq/handle.c
>> ===================================================================
>> --- linux-2.6.orig/kernel/irq/handle.c
>> +++ linux-2.6/kernel/irq/handle.c
>> @@ -82,19 +82,21 @@ static struct irq_desc irq_desc_init = {
>>
>> void init_kstat_irqs(struct irq_desc *desc, int cpu, int nr)
>> {
>> - unsigned long bytes;
>> - char *ptr;
>> int node;
>> -
>> - /* Compute how many bytes we need per irq and allocate them */
>> - bytes = nr * sizeof(unsigned int);
>> + void *ptr;
>>
>> node = cpu_to_node(cpu);
>> - ptr = kzalloc_node(bytes, GFP_ATOMIC, node);
>> - printk(KERN_DEBUG " alloc kstat_irqs on cpu %d node %d\n", cpu, node);
>> + ptr = kzalloc_node(nr * sizeof(*desc->kstat_irqs), GFP_ATOMIC, node);
>>
>> - if (ptr)
>> - desc->kstat_irqs = (unsigned int *)ptr;
>> + /*
>> + * don't overwite if can not get new one
>> + * init_copy_kstat_irqs() could still use old one
>> + */
>> + if (ptr) {
>> + printk(KERN_DEBUG " alloc kstat_irqs on cpu %d node %d\n",
>> + cpu, node);
>> + desc->kstat_irqs = ptr;
>> + }
>
> else
> init_one_irq_desc() goes BUG.
>
>> }
>
> Sorry, but it's just not acceptable for irq_to_desc_alloc_cpu() and
> init_one_irq_desc() to go BUG if a GFP_ATOMIC allocation attempt
> failed.
>
> If this code is only called on kernel boot then OK, that's acceptable.
> But if that is the case then all this code should be marked
> __init/__initdata. And ack_apic_edge() sure doesn't look like a
> boot-time-only function.
add kzalloc_node_safe()?
>
> This is basic stuff which even a cursory review should have picked up.
>
> Also, please go through all this code and convert WARN_ON(1) into
> WARN(), and convert BUG_ON(1) into BUG().
sure, will do it.
YH
next prev parent reply other threads:[~2009-02-07 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 21:50 [PATCH] irq: clear kstat_irqs Yinghai Lu
2009-02-06 22:00 ` Andrew Morton
2009-02-06 22:08 ` [PATCH] irq: clear kstat_irqs v2 Yinghai Lu
2009-02-07 7:49 ` [PATCH] irq: optimize init_kstat_irqs/init_copy_kstat_irqs Yinghai Lu
2009-02-07 8:26 ` Andrew Morton
2009-02-07 9:01 ` Yinghai Lu [this message]
2009-02-07 9:06 ` Andrew Morton
2009-02-09 8:11 ` Ingo Molnar
2009-02-09 8:19 ` Andrew Morton
2009-02-09 8:37 ` Ingo Molnar
2009-02-09 8:43 ` Andrew Morton
2009-02-09 11:34 ` Ingo Molnar
2009-02-09 8:44 ` Yinghai Lu
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=86802c440902070101l5b0ef862ja92e3f31705d9608@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®