The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Denys Vlasenko <dvlasenk@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Borislav Petkov <bp@alien8.de>, Brian Gerst <brgerst@gmail.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/signal: Deinline get_sigframe, save 240 bytes
Date: Tue, 29 Sep 2015 20:54:03 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1509292051410.4500@nanos> (raw)
In-Reply-To: <20150928202401.GB4035@linux-uzut.site>

On Mon, 28 Sep 2015, Davidlohr Bueso wrote:
> Nothing really against or in favor of these patches, but I don't think that
> saving 240 bytes (or whatever) is worth such changes, in fact we have Josh's
> tinyfication project for those systems that do in fact care.

And what exactly is wrong with slimming down the mainline kernel? We
have tons of inlines which are way too fat and an extra unconditional
function call is not going to show up as a performance degradation by
any means.

Thanks,

	tglx



  reply	other threads:[~2015-09-29 18:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 12:23 [PATCH] x86/apic: Deinline __x2apic_disable, save 467 bytes Denys Vlasenko
2015-09-28 12:23 ` [PATCH] x86: Deinline e820_type_to_string, save 126 bytes Denys Vlasenko
2015-09-30 19:57   ` [tip:x86/cleanups] x86/e820: " tip-bot for Denys Vlasenko
2015-09-28 12:23 ` [PATCH] x86: Deinline early_console_register, save 403 bytes Denys Vlasenko
2015-09-30 19:57   ` [tip:x86/cleanups] " tip-bot for Denys Vlasenko
2015-09-28 12:23 ` [PATCH] x86/signal: Deinline get_sigframe, save 240 bytes Denys Vlasenko
2015-09-28 12:33   ` H. Peter Anvin
2015-09-28 13:43     ` Denys Vlasenko
2015-09-28 20:24       ` Davidlohr Bueso
2015-09-29 18:54         ` Thomas Gleixner [this message]
2015-09-30 19:58   ` [tip:x86/cleanups] " tip-bot for Denys Vlasenko

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.1509292051410.4500@nanos \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dave@stgolabs.net \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --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