From: Thomas Gleixner <tglx@linutronix.de>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Jiang Liu <jiang.liu@linux.intel.com>,
Len Brown <len.brown@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] x86: Reduce MAX_LOCAL_APIC and MAX_IO_APICS
Date: Wed, 30 Sep 2015 19:43:23 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1509301941370.4500@nanos> (raw)
In-Reply-To: <560C0479.2080602@redhat.com>
On Wed, 30 Sep 2015, Denys Vlasenko wrote:
> On 09/30/2015 05:11 PM, Thomas Gleixner wrote:
> > On Fri, 25 Sep 2015, Denys Vlasenko wrote:
> >>
> >> +config MAX_LAPIC_ID
> >> + int "Maximum APIC ID"
> >> + range 8 32768
> >> + default "8"
> >> + ---help---
> >> + Use this option to set maximum allowed Local APIC ID higher than
> >> + maximum number of CPUs. This may be necessary for machines
> >> + with large number of processor sockets and non-contiguous
> >> + LAPIC numbering.
> >> + This setting will be automatically rounded up, if necessary.
> >
> > This is wrong. If you would limit the APIC IDs then you really break
> > stuff. You can only limit the number of APICs.
>
> This CONFIG setting allows to _increase_ max APIC ID.
NO. This is crap. I don't want to tweak a gazillion of knobs just to
build a kernel with CONFIG_NR_CPUS=8. Really not.
If you really want to make that space saving, then make it a runtime
allocation.
Thanks,
tglx
next prev parent reply other threads:[~2015-09-30 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 19:48 Denys Vlasenko
2015-09-30 15:11 ` Thomas Gleixner
2015-09-30 15:49 ` Denys Vlasenko
2015-09-30 17:03 ` Jiang Liu
2015-09-30 17:43 ` Thomas Gleixner [this message]
2015-09-30 17:18 ` Jiang Liu
2015-10-02 7:31 Daniel J Blueman
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=alpine.DEB.2.11.1509301941370.4500@nanos \
--to=tglx@linutronix.de \
--cc=dvlasenk@redhat.com \
--cc=jiang.liu@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®