From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Yinghai Lu <yinghai@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: arch_probe_nr_irqs
Date: Wed, 14 Jan 2009 12:19:49 +0100 [thread overview]
Message-ID: <20090114111949.GO2913@elte.hu> (raw)
In-Reply-To: <496BCD14.3020201@sgi.com>
* Mike Travis <travis@sgi.com> wrote:
> Yinghai Lu wrote:
> > Impact: save RAM with large NR_CPUS, get smaller nr_irqs
> >
> > Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>
> Built and tested on an 8-core intel system. Great reduction
> in NR_IRQS:
>
> [ 0.000000] NR_IRQS:33024 nr_irqs:320
>
> Thanks Yinghai!
>
> Ingo - shall I push this one as well? (If not, then you
> can add my:
>
> Acked-by: Mike Travis <travis@sgi.com>
yes, please pick it up and i can pull it from you. Please also add a
longer changelog about the precise effects and perhaps some estimations
about what the before and after situation is, and perhaps also some bits
about how it affects normal Linux users as well.
Ingo
next prev parent reply other threads:[~2009-01-14 11:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 5:42 [PATCH] x86: include apicnum.h in acpidef.h Yinghai Lu
2009-01-12 9:19 ` Ingo Molnar
2009-01-12 9:26 ` Ingo Molnar
2009-01-12 9:27 ` Ingo Molnar
2009-01-12 19:53 ` [PATCH] x86: arch_probe_nr_irqs Yinghai Lu
2009-01-12 23:07 ` Mike Travis
2009-01-14 11:19 ` Ingo Molnar [this message]
2009-01-14 19:50 ` Mike Travis
2009-01-14 20:11 ` Ingo Molnar
2009-01-14 21:26 ` Mike Travis
2009-01-15 9:49 ` Ingo Molnar
2009-01-15 20:53 ` Mike Travis
2009-01-15 21:02 ` Ingo Molnar
2009-01-12 19:09 ` [PATCH] x86: include apicnum.h in acpidef.h Mike Travis
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=20090114111949.GO2913@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=yinghai@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