public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Sergey Vlasov <vsu@altlinux.ru>
Cc: Arjan van de Ven <arjan@infradead.org>,
	discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64: Do not use -ffunction-sections for modules
Date: Wed, 21 Jun 2006 18:54:00 +0200	[thread overview]
Message-ID: <200606211854.00790.ak@suse.de> (raw)
In-Reply-To: <20060621165126.GB4126@master.mivlgu.local>

On Wednesday 21 June 2006 18:51, Sergey Vlasov wrote:

> > On Thursday 01 January 1970 01:00, Sergey Vlasov wrote:
> > > Currently CONFIG_REORDER uses -ffunction-sections for all code;
> > > however, creating a separate section for each function is not useful
> > > for modules and just adds bloat. 
> > 
> > You mean the ELF files are larger?
> 
> Yes, and all these sections are then reported in sysfs (BTW, what programs
> really use /sys/module/*/sections/* files?).

Good question. I also always considered it bloat.

> 
> > .text/.data size shouldn't > change in theory.
> 
> Actually, it does change by a small amount for some reason - even
> increases by about 100 bytes in some cases;

Ok maybe a few small vs large jumps

> however, I suppose that the 
> size reported by /proc/modules and lsmod is more important, and it
> decreases:

Ok thanks.

-Andi

      reply	other threads:[~2006-06-21 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11509074684035-git-send-email-vsu@altlinux.ru>
2006-06-21 16:41 ` [PATCH] x86_64: Do not use -ffunction-sections for modules Andi Kleen
2006-06-21 16:51   ` Sergey Vlasov
2006-06-21 16:54     ` Andi Kleen [this message]

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=200606211854.00790.ak@suse.de \
    --to=ak@suse.de \
    --cc=arjan@infradead.org \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vsu@altlinux.ru \
    /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